| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Douglas Doole <dougdoole(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Collation versioning |
| Date: | 2020-11-02 17:51:39 |
| Message-ID: | 686359.1604339499@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Hmm, a failure from dory (WIndows) during pg_upgrade:
> performing post-bootstrap initialization ... 2020-11-02 08:08:22.213
> EST [5392] FATAL: could not get collation version for locale
> "English_United States.1252": error code 87
> 87 means invalid parameter. I'm surprised it got through various
> other tests and then failed here. Whelk (also Windows) passed using
> "German_Germany.1252". Hmm. I'll wait for more Windows systems to
> report.
drongo just did it too, and it seems repeatable on dory. I'm not 100%
sure, but I think the buildfarm's initial "check" step may be run under C
locale while pg_upgrade sees whatever the machine's prevailing locale is.
If that's correct, it seems like the simplest explanation is just that
extraction of a collation version is busted for (some?) non-C locales on
Windows. Could be something as dumb as spaces in the locale name
being problematic.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-11-02 17:58:00 | Re: -O switch |
| Previous Message | Anastasia Lubennikova | 2020-11-02 17:45:37 | Re: RE: Delaying/avoiding BTreeTupleGetNAtts() call within _bt_compare() |