Re: [PATCH] Fix search_path default value separator. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH] Fix search_path default value separator.
Date
Msg-id CA+TgmoYxFYKY017yrqEZMQb7Miv=twR9PWpo3CUsAoxRiGDe6w@mail.gmail.com
Whole thread Raw
In response to [PATCH] Fix search_path default value separator.  (Christoph Martin <christoph.r.martin@gmail.com>)
Responses Re: [PATCH] Fix search_path default value separator.  (Christoph Martin <christoph.r.martin@gmail.com>)
List pgsql-hackers
On Fri, Jul 11, 2014 at 6:09 AM, Christoph Martin
<christoph.r.martin@gmail.com> wrote:
> I noticed a minor inconsistency with the search_path separator used in the
> default configuration.
>
> The schemas of any search_path set using `SET search_path TO...` are
> separated by ", " (comma, space), while the default value is only separated
> by "," (comma).
>
> The attached patch against master changes the separator of the default value
> to be consistent with the usual comma-space separators, and updates the
> documentation of `SHOW search_path;` accordingly.
>
> This massive three-byte change passes all 144 tests of make check.

Heh.  I'm not particularly averse to changing this, but I guess I
don't see any particular benefit of changing it either.  Either comma
or comma-space is a legal separator, so why worry about it?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Use unique index for longer pathkeys.
Next
From: Christoph Martin
Date:
Subject: Re: [PATCH] Fix search_path default value separator.