Re: SQL_ASCII / LATIN1 - Mailing list pgsql-novice

From Tom Lane
Subject Re: SQL_ASCII / LATIN1
Date
Msg-id 3684.1074093186@sss.pgh.pa.us
Whole thread Raw
In response to SQL_ASCII / LATIN1  (Aarni Ruuhimäki <aarni.ruuhimaki@kymi.com>)
Responses Re: SQL_ASCII / LATIN1  (Aarni Ruuhimäki <aarni.ruuhimaki@kymi.com>)
Re: SQL_ASCII / LATIN1  (Aarni Ruuhimäki <aarni.ruuhimaki@kymi.com>)
List pgsql-novice
Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <aarni.ruuhimaki@kymi.com> writes:
> When I pg_dump -c trouble > trouble_dump, take the file down and
> cat trouble_dump | psql trouble it shows as LATIN1 in the local listing. Then
> I dump it again locally, upload and cat, it shows as SQL_ASCII.

I believe the default encoding for a newly-created database is the same
encoding as template1 --- since the two installations were initdb'd with
different default encodings, the behavior you're describing is not too
surprising.  You can specify the encoding to use when you create a
database, though.

BTW, 7.3.3 has a serious known bug in the restart logic ... you ought to
update to 7.3.4 or 7.3.5 before you get bitten.

            regards, tom lane

pgsql-novice by date:

Previous
From: Oliver Elphick
Date:
Subject: Re: probs with 7.3 -> 7.4 on debian
Next
From: Ralf Bortfeldt
Date:
Subject: parser-error