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

Re: Add switches for DELIMITER and NULL in pg_dump COPY

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>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Add switches for DELIMITER and NULL in pg_dump COPY
Date: 2006-03-08 16:26:00
Message-ID: 15791.1141835160@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
David Fetter <david(at)fetter(dot)org> writes:
> On Wed, Mar 08, 2006 at 11:03:00AM -0500, Tom Lane wrote:
>> Did anyone provide a convincing use case for this?

> I've had one so far, and it was enough to cause me to make a special
> patched version of pg_dump.  To get some idea of how drastic that was,
> consider that I think it's generally bad practice to compile from
> source because it can take you too far off the "generally supported
> software" map.  The case I had was making a database with a schema and
> initial data whose dump output gets checked into a source code
> management system.

So?  Don't tell me your SCMS can't handle tabs.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: David FetterDate: 2006-03-08 16:29:55
Subject: Re: Add switches for DELIMITER and NULL in pg_dump COPY
Previous:From: Tom LaneDate: 2006-03-08 16:20:50
Subject: Re: Merge algorithms for large numbers of "tapes"

pgsql-patches by date

Next:From: David FetterDate: 2006-03-08 16:29:55
Subject: Re: Add switches for DELIMITER and NULL in pg_dump COPY
Previous:From: David FetterDate: 2006-03-08 16:20:39
Subject: Re: [PATCHES] Add switches for DELIMITER and NULL in pg_dump COPY

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