Re: SQL_ASCII / LATIN1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: aarni(dot)ruuhimaki(at)kymi(dot)com
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: SQL_ASCII / LATIN1
Date: 2004-01-14 15:13:06
Message-ID: 3684.1074093186@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <aarni(dot)ruuhimaki(at)kymi(dot)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

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Ralf Bortfeldt 2004-01-14 16:35:48 parser-error
Previous Message Oliver Elphick 2004-01-14 15:08:22 Re: probs with 7.3 -> 7.4 on debian