From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | Kern Sibbald <kern(at)sibbald(dot)com>, pgsql-general(at)postgresql(dot)org, bacula-devel <bacula-devel(at)lists(dot)sourceforge(dot)net>, bacula-users <bacula-users(at)lists(dot)sourceforge(dot)net> |
Subject: | Re: Catastrophic changes to PostgreSQL 8.4 |
Date: | 2009-12-03 03:03:18 |
Message-ID: | 27804.1259809398@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> It's a pity that attempting to specify an encoding other than the safe
> one when using a non-template0 database doesn't cause the CREATE
> DATABASE command to fail with an error.
Huh?
regression=# create database foo lc_ctype = 'en_US.utf8' encoding = 'latin1';
ERROR: encoding LATIN1 does not match locale en_US.utf8
DETAIL: The chosen LC_CTYPE setting requires encoding UTF8.
As best I can tell, the OP is complaining exactly because it did fail,
in contrast to pre-8.4 versions that let him create unsafe combinations.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jerome Alet | 2009-12-03 03:09:29 | Re: [Bacula-users] Catastrophic changes to PostgreSQL 8.4 |
Previous Message | Craig Ringer | 2009-12-03 03:02:12 | Re: Auto Vacuum Daemon |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-12-03 03:04:22 | Re: CommitFest status/management |
Previous Message | Tom Lane | 2009-12-03 02:55:42 | Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a |