Re: Catastrophic changes to PostgreSQL 8.4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kern Sibbald <kern(at)sibbald(dot)com>
Cc: Sam Mason <sam(at)samason(dot)me(dot)uk>, 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-04 14:42:38
Message-ID: 23793.1259937758@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Kern Sibbald <kern(at)sibbald(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Cjkalbente 2009-12-04 15:08:16 Re: Daily migration on Postgresql
Previous Message Kern Sibbald 2009-12-04 14:26:08 Re: Catastrophic changes to PostgreSQL 8.4

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-12-04 14:46:01 Re: Block-level CRC checks
Previous Message Kern Sibbald 2009-12-04 14:26:08 Re: Catastrophic changes to PostgreSQL 8.4