From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mija Lee <mija@scharp.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: -d option in pg_dump
Date: Tue, 08 Jan 2008 17:23:01 -0500
Message-ID: <14955.1199830981@sss.pgh.pa.us> (raw)
In-Reply-To: <4783DDD7.2030900@scharp.org>
References: <4783DDD7.2030900@scharp.org>
Mija Lee <mija@scharp.org> 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
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, mija@scharp.org
Subject: Re: -d option in pg_dump
In-Reply-To: <14955.1199830981@sss.pgh.pa.us>
* 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