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@sss.pgh.pa.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@kinesis-cem.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