From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christian Fowler <spider@viovio.com>
Cc: pgsql-admin list <pgsql-admin@postgresql.org>
Subject: Re: evil characters #bfef cause dump failure
Date: Mon, 15 Nov 2004 14:44:49 -0500
Message-ID: <9996.1100547889@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com>
References: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com>
Christian Fowler <spider@viovio.com> writes:
> After much wrestling, it appears the hex byte sequence #bfef in a VARCHAR
> column causes a truncated COPY line to be written (and thus the *entire*
> COPY block fails).
What database encoding and locale are you using?
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, spider@viovio.com
Subject: Re: evil characters #bfef cause dump failure
In-Reply-To: <9996.1100547889@sss.pgh.pa.us>
References: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com> <9996.1100547889@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