From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Rural Hunter <ruralhunter(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed |
Date: | 2012-09-24 12:55:00 |
Message-ID: | 20120924125500.GA21242@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
On Sun, Sep 23, 2012 at 06:46:33PM -0400, Peter Eisentraut wrote:
> On Sun, 2012-09-23 at 22:20 +0800, Rural Hunter wrote:
> > Ah yes, seems I used a wrong parameter. The --locale='zh_CN.utf8'
> > works. --locale='zh_CN.UTF8' also works. But still the question is,
> > should the encoding name be case sensitive?
>
> PostgreSQL treats encoding names as case insensitive.
>
> But it depends on the operating system whether locale names are case
> sensitive.
I can confirm that pg_upgrade does case-insensitive comparisons of
encoding/locale names:
static void
check_locale_and_encoding(ControlData *oldctrl,
ControlData *newctrl)
{
/* These are often defined with inconsistent case, so use pg_strcasecmp(). */
if (pg_strcasecmp(oldctrl->lc_collate, newctrl->lc_collate) != 0)
pg_log(PG_FATAL,
"old and new cluster lc_collate values do not match\n");
if (pg_strcasecmp(oldctrl->lc_ctype, newctrl->lc_ctype) != 0)
pg_log(PG_FATAL,
"old and new cluster lc_ctype values do not match\n");
if (pg_strcasecmp(oldctrl->encoding, newctrl->encoding) != 0)
pg_log(PG_FATAL,
"old and new cluster encoding values do not match\n");
}
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Johnny Tan | 2012-09-24 13:05:11 | changes to postgresql.conf |
Previous Message | John Coryat | 2012-09-24 11:50:01 | Re: Multiple servers with Postgresql |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2012-09-24 13:06:04 | Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed |
Previous Message | Andres Freund | 2012-09-24 11:37:59 | Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes |