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

From Tom Lane
Subject Re: Proposal: new pg_dump options --copy-delimiter and
Date
Msg-id 3996.1138387404@sss.pgh.pa.us
Whole thread Raw
In response to Re: Proposal: new pg_dump options --copy-delimiter and  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Proposal: new pg_dump options --copy-delimiter and  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> I could not disagree more. The invisibility of tabs makes their use as a
> delimiter wholly evil. I have lost count of the number of corrupted
> makefiles etc. I have seen because a tab got converted to a space and it
> was impossible to tell.

> More tears have been shed over tabs used than tabs unused. (Apologies to
> St Theresa).

That line of argument leads to the suggestion that pg_dump should just
use something else (I'd vote for "|"), all the time, in order to produce
more robust dump files.  I still don't see the argument for exposing
a switch though.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Proposal: new pg_dump options --copy-delimiter and
Next
From: Andrew Dunstan
Date:
Subject: Re: Proposal: new pg_dump options --copy-delimiter and