pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christian Fowler <spider@viovio.com>
To: pgsql-admin list <pgsql-admin@postgresql.org>
Subject: evil characters #bfef cause dump failure
Date: Mon, 15 Nov 2004 12:46:19 -0500 (EST)
Message-ID: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com> (raw)


I have been trying to track down the source of why my 7.4.5 database won't 
reimport it's own dump ( http://archives.postgresql.org/pgsql-admin/2004-10/msg00213.php )

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). Exporting as inserts did not fix the problem either.

Any thoughts on why this might be so or how it can be avoided? Evil 
thought of the day is if someone were to go around and paste this 
multi-byte character in various websites' html forms it could cause a lot 
of trouble.

Also, the behavior of the restore / psql import to complete the COPY 
fields from the *following* line seems not good. It would be nice if the 
missing columns could just be written as NULL's. 6 bad rows makes a 6 gig 
dump worthless. Or perhaps an option to import each copy row in it's own 
transaction so 5+ million copied rows don't fail for 6 bogus ones. Perhaps a
--this_is_an_emergency_so_please_do_everything_you_can_to_restore_as_much_as_possible
option.

If any of the core dev's want some small debug dumps I created, I'd be 
happy to pass them on.

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



view thread (16+ messages)  latest in thread

Message-ID: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com>
Permalink:  ../Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com/
Also on:    postgresql.org/message-id/Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com

 · 

reply

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: spider@viovio.com
  Subject: Re: evil characters #bfef cause dump failure
  In-Reply-To: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com>
  References: <Pine.LNX.4.61.0411150335350.10091@leda.steelsun.com>

* 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