Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Rural Hunter <ruralhunter@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-09-24T15:28:59Z
Lists: pgsql-hackers
On Mon, Sep 24, 2012 at 11:24:04AM -0400, Peter Eisentraut wrote: > On 9/24/12 10:13 AM, Tom Lane wrote: > > FWIW, what I found out last time I touched this code is that on many > > systems setlocale doesn't bother to return a canonicalized spelling; > > it just gives back the string you gave it. It might be worth doing > > what Peter suggests, just to be consistent with what we are doing > > elsewhere, but I'm not sure how much it will help. > > It might not have anything to do with the current problem, but if initdb > canonicalizes locale names, then pg_upgrade also has to. Otherwise, > whenever an operating system changes its locale canonicalization rules, > pg_upgrade will fail. Agreed. I will work on that soon. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Replace empty locale name with implied value in CREATE DATABASE and initdb.
- c7cea267de3c 9.2.0 cited