Skip site navigation (1) Skip section navigation (2)

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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 19:05:09
Message-ID: 1138388709.3074.35.camel@swithin (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, 2006-01-27 at 13:43 -0500, Tom Lane wrote:
> 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.

If we regard them as suitable for human editing for normal use, yes.



In response to


pgsql-hackers by date

Next:From: Jeff TroutDate: 2006-01-27 19:06:05
Subject: Re: Segfault Exiting psql
Previous:From: Tom LaneDate: 2006-01-27 18:43:24
Subject: Re: Proposal: new pg_dump options --copy-delimiter and

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group