Re: [BUGS] initdb stores default client_encoding from environment-variable

2010-04-14 Thread Tom Lane
"Wolfgang.Koenig" writes: > initdb stores default client_encoding from environment-variable > Postgres Version: 8.4.3 and 8.3.6 > Operating System: Sun Solaris 5.10 and SuseEnterprise 9 > When a database is initialized with the initdb-command, the default > client_enconding, which will be stored

Re: [BUGS] initdb stores default client_encoding from environment-variable

2010-04-14 Thread Bruce Momjian
Perhaps this is some Solaris-specific change he is seeing. --- Craig Ringer wrote: > [re-posting as I mistakenly sent this only to the OP] > > On 09/04/10 16:49, Wolfgang.Koenig wrote: > > initdb stores default client_encod

Re: [BUGS] initdb stores default client_encoding from environment-variable

2010-04-12 Thread Craig Ringer
[re-posting as I mistakenly sent this only to the OP] On 09/04/10 16:49, Wolfgang.Koenig wrote: initdb stores default client_encoding from environment-variable Postgres Version: 8.4.3 and 8.3.6 Operating System: Sun Solaris 5.10 and SuseEnterprise 9 When a database is initialized with the ini

Re: [BUGS] initdb stores default client_encoding from environment-variable

2010-04-12 Thread Robert Haas
On Fri, Apr 9, 2010 at 4:49 AM, Wolfgang.Koenig wrote: > When a database is initialized with the initdb-command, the default > client_enconding, which will be stored in the DB, depends on the value > of the environment-variable PGCLIENTENCODING at the time of running > initdb. This behaviour is no

[BUGS] initdb stores default client_encoding from environment-variable

2010-04-09 Thread Wolfgang.Koenig
initdb stores default client_encoding from environment-variable Postgres Version: 8.4.3 and 8.3.6 Operating System: Sun Solaris 5.10 and SuseEnterprise 9 When a database is initialized with the initdb-command, the default client_enconding, which will be stored in the DB, depends on the value of