| From: | Christoph Martin <christoph(dot)r(dot)martin(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | [PATCH] Fix search_path default value separator. |
| Date: | 2014-07-11 10:09:04 |
| Message-ID: | CA+XL1YsUNUthjVX33Qe_=+VbrTBMO0MHC3pHtdnh-Lp9cTiR0A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
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.
Regards,
Christoph
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fix-search_path-default-value-separator.patch | text/x-patch | 2.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2014-07-11 10:21:32 | Re: No exact/lossy block information in EXPLAIN ANALYZE for a bitmap heap scan |
| Previous Message | David Rowley | 2014-07-11 09:54:22 | Re: Allowing join removals for more join types |