From: | "Peter Darley" <pdarley(at)kinesis-cem(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Pgsql-Admin" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Can't dump and restore |
Date: | 2005-11-01 21:52:10 |
Message-ID: | PDEOIIFFBIAABMGNJAGPGEFBDPAA.pdarley@kinesis-cem.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom,
You're correct, the new database was being created as UNICODE instead of
SQL_ASCII. I'd never messed with encoding before, but I guess that the
default was changed some time after I originally made the database on 6.x.
Stupid mistake. :)
Thanks a bundle for your help!
Peter Darley
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, November 01, 2005 1:38 PM
To: Peter Darley
Cc: Pgsql-Admin
Subject: Re: [ADMIN] Can't dump and restore
"Peter Darley" <pdarley(at)kinesis-cem(dot)com> writes:
> So, long and short, I think that everything should be SQL_ASCII, but even
> when it is, I get the error.
There is no way you're going to get that error if the encoding setting
is SQL_ASCII, so better look again. "SHOW server_encoding" and "SHOW
client_encoding" might be revealing.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tzvetan Tzankov | 2005-11-01 23:22:55 | Re: UNIQUE KEY with null value... |
Previous Message | Peter Darley | 2005-11-01 21:40:06 | Re: Can't dump and restore |