| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Greg Stark <gsstark(at)mit(dot)edu>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: new pg_dump options --copy-delimiter and |
| Date: | 2006-01-27 18:43:24 |
| Message-ID: | 3996.1138387404@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2006-01-27 19:05:09 | Re: Proposal: new pg_dump options --copy-delimiter and |
| Previous Message | Andrew Dunstan | 2006-01-27 18:22:22 | Re: Proposal: new pg_dump options --copy-delimiter and |