Re: Catastrophic changes to PostgreSQL 8.4 - Mailing list pgsql-general

From Tom Lane
Subject Re: Catastrophic changes to PostgreSQL 8.4
Date
Msg-id 27804.1259809398@sss.pgh.pa.us
Whole thread Raw
In response to Re: Catastrophic changes to PostgreSQL 8.4  (Craig Ringer <craig@postnewspapers.com.au>)
Responses Re: Catastrophic changes to PostgreSQL 8.4  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-general
Craig Ringer <craig@postnewspapers.com.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

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Auto Vacuum Daemon
Next
From: Craig Ringer
Date:
Subject: Re: using querys like: 'select table.*'