Re: evil characters #bfef cause dump failure
От
Christian Fowler
Тема
Re: evil characters #bfef cause dump failure
Дата
Msg-id
Pine.LNX.4.61.0411151527550.12980@leda.steelsun.com
Ответ на
Re: evil characters #bfef cause dump failure (Tom Lane)
Список
Дерево обсуждения
evil characters #bfef cause dump failure Christian Fowler <spider@viovio.com>
Re: evil characters #bfef cause dump failure Tom Lane <tgl@sss.pgh.pa.us>
Re: evil characters #bfef cause dump failure Christian Fowler <spider@viovio.com>
Re: evil characters #bfef cause dump failure Tom Lane <tgl@sss.pgh.pa.us>
Re: evil characters #bfef cause dump failure Christian Fowler <spider@viovio.com>
Re: evil characters #bfef cause dump failure Tom Lane <tgl@sss.pgh.pa.us>
Re: evil characters #bfef cause dump failure Markus Bertheau <twanger@bluetwanger.de>
[shell]$ env PGCLIENTENCODING=UNICODE LANG=en_US.UTF-8 db=# \encoding UNICODE On Mon, 15 Nov 2004, Tom Lane wrote: > Christian Fowler 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 по дате отправления