From: | Stefan Sassenberg <stefan(dot)sassenberg(at)gmx(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: ERRORDATA_STACK_SIZE exceeded |
Date: | 2006-10-18 08:53:03 |
Message-ID: | 4535EB6F.3080105@gmx.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Stefan Sassenberg <stefan(dot)sassenberg(at)gmx(dot)de> writes:
>> de_DE(at)euro is ISO-8859-15, if that helps. I changed the locale to
>> en_US.UTF-8 and LC_CTYPE in the environment is set to that value too.
>> Nevertheless "show lc_ctype" says de_DE(at)euro, even after a postgresql
>> restart. How can I change that?
>
> initdb is the only way to change the database's LC_CTYPE or LC_COLLATE :-(
That's ok for now, I can do so [type type type].
Done. Fine, now my script runs perfectly. Thanks to all who answered.
In the initdb man pages I saw that I can set locale variables, so
there's no need to switch my entire environment to a locale that I don't
want. Is it a necessary restriction that the db encoding must match the
lc_ctype? I can remember a case when I had two dbs with different
encodings and this might happen again. Or is it a problem that I'm using
a localized version of postgresql that uses special characters in the
messages?
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Ilja Golshtein | 2006-10-18 08:56:10 | Re: COPY FROM STDIN instead of INSERT |
Previous Message | Matthias.Pitzl | 2006-10-18 08:48:37 | Re: Maximum size of database |