Re: Proposal: new pg_dump options --copy-delimiter and --copy-null

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Fetter <david(at)fetter(dot)org>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: new pg_dump options --copy-delimiter and --copy-null
Date: 2006-01-27 14:12:11
Message-ID: 1626.1138371131@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Fetter <david(at)fetter(dot)org> writes:
> On Thu, Jan 26, 2006 at 10:17:05PM -0500, Tom Lane wrote:
>> Seems to me that "psql -c 'COPY ...'" is a more likely front-end for
>> such a process.

> Actually, it's not. I'm attaching my preliminary patch, as I see I
> haven't explained it well enough.

The patch conveys nothing you didn't explain already, and I still don't
see why one would use pg_dump instead of psql. If you use pg_dump then
you have to cope with a pile of random SQL and comments as well as the
actual data.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-01-27 14:26:48 stats for failed transactions (was Re: [GENERAL] VACUUM Question)
Previous Message Adnan DURSUN 2006-01-27 10:25:57 unsubscribe