Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Peter Eisentraut <peter_e@gmx.net>, Rural Hunter <ruralhunter@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-09-24T14:13:45Z
Lists: pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes: >>> I can confirm that pg_upgrade does case-insensitive comparisons of >>> encoding/locale names: > Or we could just remove dashes from the name before comparisons. That would merely move the breakage somewhere else. I think you are already assuming far too much about the OS' interpretation of locale names by assuming they are case-insensitive. Assuming that dashes aren't significant seems 100% wrong. 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. regards, tom lane
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