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 23793.1259937758@sss.pgh.pa.us
Whole thread Raw
In response to Catastrophic changes to PostgreSQL 8.4  (Kern Sibbald <kern@sibbald.com>)
List pgsql-general
Kern Sibbald <kern@sibbald.com> writes:
> Concerning the future: I am still a bit concerning about the mention in the
> document of possible future changes concerning SQL_ASCII and LC_CTYPE not C
> or POSIX ("Using this combination of settings is deprecated and may someday
> be forbidden altogether. "), so if you have any suggestions for CREATE
> DATABASE that we can use now that will ensure that for future versions of
> Bacula + PostgreSQL that we will end up with our bacula database created with
> SQL_ASCII, I would much appreciate it.

What you need to do is add
    LC_COLLATE = 'C' LC_CTYPE = 'C'
to the command.  This is already important in 8.4 to ensure the command
won't fail if the installation default locale is not C.

The difficulty of course is that this is only for 8.4 and up, older
versions won't take it.  I don't know the context well enough to suggest
how you might want to deal with version-sensitive commands (probably you
have some plan for that already).

            regards, tom lane

pgsql-general by date:

Previous
From: Howard Cole
Date:
Subject: Re: Unexpected EOF on client connection
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Installing PL/pgSQL by default