From: Tom Lane <tgl@sss.pgh.pa.us>
To: Phillip Smith <phillip.smith@weatherbeeta.com.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres Backup and Restore
Date: Sun, 10 Feb 2008 19:28:35 -0500
Message-ID: <12050.1202689715@sss.pgh.pa.us> (raw)
In-Reply-To: <00e401c86c40$9da2fb70$9b0014ac@wbaus090>
References: <00e401c86c40$9da2fb70$9b0014ac@wbaus090>
"Phillip Smith" <phillip.smith@weatherbeeta.com.au> writes:
> How has the software been misinformed and how can we avoid it then? :)
Well, if that were entirely clear then we could fix it.
> The start of the pgdump sets the client encoding, so shouldn't that tell PG
> that things could get strange?
The problems seem to arise when the data doesn't actually have the
claimed encoding. We've been gradually tightening the encoding checks
over the years, so data that older versions let pass without comment
might now be recognized as malformed. In the OP's case there may be
something else going on (such as an actual encoding-conversion bug).
I've encouraged him to try to trace things forward from his original
input data and see if we can find out exactly where it went off the
rails.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, phillip.smith@weatherbeeta.com.au
Subject: Re: Postgres Backup and Restore
In-Reply-To: <12050.1202689715@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox