[HACKERS] Default Locale in initdb

2004-06-02 Thread pgsql
Is it me or has the default locale of created databases change at some point? Currently, on Linux, if one does not specify a locale, the locale is taken from the system environment and it is not C. While I can both sides of a discussion, I think that choosing a locale without one being specified

Re: [HACKERS] Default Locale in initdb

2004-06-02 Thread Andrew Dunstan
[EMAIL PROTECTED] wrote: Is it me or has the default locale of created databases change at some point? Currently, on Linux, if one does not specify a locale, the locale is taken from the system environment and it is not C. While I can both sides of a discussion, I think that choosing a locale

Re: [HACKERS] Default Locale in initdb

2004-06-02 Thread Paul Ramsey
Just because it is not new does not mean that it is good. When this new behavior was introduced, and I migrated our databases to the new PgSQL version (dump/restore), the locale of all my databases were silently changed from C to US_en. This broke one application in a very subtle way because of

Re: [HACKERS] Default Locale in initdb

2004-06-02 Thread Stephan Szabo
On Wed, 2 Jun 2004 [EMAIL PROTECTED] wrote: Is it me or has the default locale of created databases change at some point? Currently, on Linux, if one does not specify a locale, the locale is taken from the system environment and it is not C. While I can both sides of a discussion, I think

Re: [HACKERS] Default Locale in initdb

2004-06-02 Thread Andrew Dunstan
Paul Ramsey wrote: Just because it is not new does not mean that it is good. Sure. I've been caught by it too. Once. :-) When this new behavior was introduced, and I migrated our databases to the new PgSQL version (dump/restore), the locale of all my databases were silently changed from C to

Re: [HACKERS] Default Locale in initdb

2004-06-02 Thread Christopher Kings-Lynne
When this new behavior was introduced, and I migrated our databases to the new PgSQL version (dump/restore), the locale of all my databases were silently changed from C to US_en. This broke one application in a very subtle way because of slightly different sort behavior in the different

Re: [HACKERS] Default Locale in initdb

2004-06-02 Thread Bruce Momjian
Christopher Kings-Lynne wrote: When this new behavior was introduced, and I migrated our databases to the new PgSQL version (dump/restore), the locale of all my databases were silently changed from C to US_en. This broke one application in a very subtle way because of slightly different

Re: [HACKERS] Default Locale in initdb

2004-06-02 Thread pgsql
Christopher Kings-Lynne wrote: When this new behavior was introduced, and I migrated our databases to the new PgSQL version (dump/restore), the locale of all my databases were silently changed from C to US_en. This broke one application in a very subtle way because of slightly different

Re: [HACKERS] Default Locale in initdb

2004-06-02 Thread Christopher Kings-Lynne
This has bitten me a couple times. In what version did it change? My feeling, and I'd like to see what everyone else thinks, is that if you do not specify a locale, you get C. I think that initdb should default to something, and do the following: * Have an explicit warnign if no locale specified,

Re: [HACKERS] Default Locale in initdb

2004-06-02 Thread Andrew Dunstan
Christopher Kings-Lynne wrote: This has bitten me a couple times. In what version did it change? My feeling, and I'd like to see what everyone else thinks, is that if you do not specify a locale, you get C. I think that initdb should default to something, and do the following: * Have an