Re: evil characters #bfef cause dump failure - Mailing list pgsql-admin

From Christian Fowler
Subject Re: evil characters #bfef cause dump failure
Date
Msg-id Pine.LNX.4.61.0411151527550.12980@leda.steelsun.com
Whole thread Raw
In response to Re: evil characters #bfef cause dump failure  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: evil characters #bfef cause dump failure
List pgsql-admin
[shell]$ env
PGCLIENTENCODING=UNICODE
LANG=en_US.UTF-8

db=# \encoding
UNICODE


On Mon, 15 Nov 2004, Tom Lane wrote:

> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

[ \ /
[ >X<   Christian Fowler      | spider AT viovio.com
[ / \   http://www.viovio.com | http://www.tikipro.org

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: evil characters #bfef cause dump failure
Next
From: Tom Lane
Date:
Subject: Re: evil characters #bfef cause dump failure