| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Changes to pg_dump/psql following collation "C" in the catalog |
| Date: | 2019-04-04 23:43:43 |
| Message-ID: | 24402.1554421423@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Daniel Verite" <daniel(at)manitou-mail(dot)org> writes:
> I think psql and pg_dump need to adjust, just like the 3rd party tools
> will, at least those that support collation-aware search in the catalog.
> PFA a patch that implements the slight changes needed.
> I'll add an entry for it in the next CF.
Hm, if that's as much as we have to touch, I think there's a good
argument for squeezing it into v12 rather than waiting. The point
here is mostly to avoid a behavior change from pre-v12, but if we
allow v12 to have a different behavior, it's questionable whether
we'd want v13 to change it back.
Just looking at the patch, I wonder whether it doesn't need some
server-version checks. At the very least this would break with
pre-9.1 servers, which lack COLLATE altogether.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2019-04-04 23:59:06 | Re: COPY FROM WHEN condition |
| Previous Message | Andres Freund | 2019-04-04 23:31:54 | Re: COPY FROM WHEN condition |