Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 8C8ED2E2D85 for ; Tue, 8 Jan 2008 18:23:06 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 15285-06 for ; Tue, 8 Jan 2008 18:23:02 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 4CACE2E01C8 for ; Tue, 8 Jan 2008 18:23:02 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id m08MN1Kk014956; Tue, 8 Jan 2008 17:23:01 -0500 (EST) To: Mija Lee cc: pgsql-admin@postgresql.org Subject: Re: -d option in pg_dump In-reply-to: <4783DDD7.2030900@scharp.org> References: <4783DDD7.2030900@scharp.org> Comments: In-reply-to Mija Lee message dated "Tue, 08 Jan 2008 12:32:23 -0800" Date: Tue, 08 Jan 2008 17:23:01 -0500 Message-ID: <14955.1199830981@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/92 X-Sequence-Number: 27866 Mija Lee writes: > In previous versions of postgres (8.1, 8.0), we had problems loading > some data from dumps that were used the copy command rather than the > insert command. If I remember correctly, these problems were caused by > weird characters in some of the data values. As a result, we tend to use > the -d option with pg_dump. As far as I can find from a quick look through the CVS logs, no data-mangling bug in COPY has been reported or fixed since before 7.4 (at least in the mainline code --- CSV mode has had some teething pains, but pg_dump has never used CSV mode). The last patch I can find that addressed any such problem was here: http://archives.postgresql.org/pgsql-committers/2003-10/msg00050.php If you've had issues since then, you really should have filed bug reports. regards, tom lane