| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Add function to import operating system collations |
| Date: | 2017-01-18 17:26:40 |
| Message-ID: | 1b7a27c7-5c81-541f-ae51-0282ab8cd5e9@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 1/18/17 12:23 PM, Peter Eisentraut wrote:
> Yeah, it's supposed to do that. Note that the second call to
> CollationCreate() in pg_import_system_collations() has the "if not
> exists" argument true regardless. So the error appears to come from the
> first one.
>
> What's fishy about this is that I can't reproduce it locally in a
> variety of VMs, and the buildfarm is not unanimous either.
OK, the problem has to do with the order of the locale -a output, which
is in turn dependent on the current locale.
I'll think of something.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-01-18 17:37:01 | Re: pgsql: Add function to import operating system collations |
| Previous Message | Peter Eisentraut | 2017-01-18 17:23:24 | Re: pgsql: Add function to import operating system collations |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-01-18 17:37:01 | Re: pgsql: Add function to import operating system collations |
| Previous Message | Peter Eisentraut | 2017-01-18 17:23:24 | Re: pgsql: Add function to import operating system collations |