Stefan Sassenberg <[EMAIL PROTECTED]> writes:
> Is it a necessary restriction that the db encoding must match the
> lc_ctype?
If you set the LC_ variables to "C" you can get away with using
different encodings, but I wouldn't recommend it for any other locale
setting. Aside from the message tran
Tom Lane wrote:
Stefan Sassenberg <[EMAIL PROTECTED]> writes:
[EMAIL PROTECTED] 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 [EMAIL PROTECTED], even after a postgresql
restart. How
Stefan Sassenberg <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] 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 [EMAIL PROTECTED], even after a postgresql
> restart. How can I cha
Tom Lane wrote:
Stefan Sassenberg <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
What LC_CTYPE and LC_MESSAGES settings are you using? We've seen
problems of this ilk when gettext() produces messages encoded in the
"wrong" encoding (ie, not what the database encoding is).
postgresql.log says [
Stefan Sassenberg <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> What LC_CTYPE and LC_MESSAGES settings are you using? We've seen
>> problems of this ilk when gettext() produces messages encoded in the
>> "wrong" encoding (ie, not what the database encoding is).
> postgresql.log says [...] [EMA
Hello Tom,
Tom Lane wrote:
Stefan Sassenberg <[EMAIL PROTECTED]> writes:
PANIK: ERRORDATA_STACK_SIZE exceeded
server closed the connection unexpectedly
What LC_CTYPE and LC_MESSAGES settings are you using? We've seen
problems of this ilk when gettext() produces messages encoded in the
"wron
Stefan Sassenberg <[EMAIL PROTECTED]> writes:
> PANIK: ERRORDATA_STACK_SIZE exceeded
> server closed the connection unexpectedly
What LC_CTYPE and LC_MESSAGES settings are you using? We've seen
problems of this ilk when gettext() produces messages encoded in the
"wrong" encoding (ie, not what th
Hello Shane,
Shane Ambler wrote:
Stefan Sassenberg wrote:
Hello,
I've got a failing sql-Script that I execute with the psql command.
The Script contains:
8<-
SET CLIENT_ENCODING = 'LATIN1';
The database that script is applied to i
Stefan Sassenberg wrote:
Hello,
I've got a failing sql-Script that I execute with the psql command. The
Script contains:
8<-
SET CLIENT_ENCODING = 'LATIN1';
The database that script is applied to is UTF8 encoded.
Stefan Sassenberg
Hallo Markus,
Markus Schiltknecht wrote:
Hallo Stefan,
Stefan Sassenberg wrote:
Hello,
I've got a failing sql-Script that I execute with the psql command.
The Script contains:
I've been unable to reproduce the error with just that snippet (on
debian with PostgreSQL 8.1.4). Can you provid
Hallo Stefan,
Stefan Sassenberg wrote:
Hello,
I've got a failing sql-Script that I execute with the psql command. The
Script contains:
I've been unable to reproduce the error with just that snippet (on
debian with PostgreSQL 8.1.4). Can you provide a stripped down test case?
---
Hello,
I've got a failing sql-Script that I execute with the psql command. The
Script contains:
8<-
SET CLIENT_ENCODING = 'LATIN1';
(Some other statements)
CREATE TABLE "public"."init_camera_type" (
"id_camera_type" SMALLINT NOT NULL,
12 matches
Mail list logo
