Re: Proposal: new pg_dump options --copy-delimiter and --copy-null - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Proposal: new pg_dump options --copy-delimiter and --copy-null
Date
Msg-id 26997.1138331825@sss.pgh.pa.us
Whole thread Raw
In response to Proposal: new pg_dump options --copy-delimiter and --copy-null  (David Fetter <david@fetter.org>)
Responses Re: Proposal: new pg_dump options --copy-delimiter and --copy-null
List pgsql-hackers
David Fetter <david@fetter.org> writes:
> I have seed database scripts quasi-generated from pg_dump which
> include COPY statements, but the data is hard to edit (especially cut
> & paste operations) when the COPY delimiter is some non-visible
> character like \t.

This seems like an awfully weak use-case for adding to pg_dump's already
overly complicated feature set.  The difficulty of parsing COPY output
is not simplified by making the delimiter variable --- more likely the
reverse.  Furthermore, it's quite unclear why you'd use pg_dump at all
to generate a data file that you intend to feed to some other program.
Seems to me that "psql -c 'COPY ...'" is a more likely front-end for
such a process.
        regards, tom lane


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Proposal: new pg_dump options --copy-delimiter and --copy-null
Next
From: David Fetter
Date:
Subject: Re: Proposal: new pg_dump options --copy-delimiter and --copy-null