Skip site navigation (1) Skip section navigation (2)

Re: evil characters #bfef cause dump failure

From: Christian Fowler <spider(at)viovio(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christian Fowler <spider(at)viovio(dot)com>,pgsql-admin list <pgsql-admin(at)postgresql(dot)org>
Subject: Re: evil characters #bfef cause dump failure
Date: 2004-11-15 20:29:38
Message-ID: Pine.LNX.4.61.0411151527550.12980@leda.steelsun.com (view raw or flat)
Thread:
Lists: 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(at)viovio(dot)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

In response to

Responses

pgsql-admin by date

Next:From: Tom LaneDate: 2004-11-15 20:35:46
Subject: Re: evil characters #bfef cause dump failure
Previous:From: Tom LaneDate: 2004-11-15 19:44:49
Subject: Re: evil characters #bfef cause dump failure

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group