| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-03-08 16:29:55 | Re: Add switches for DELIMITER and NULL in pg_dump COPY |
| Previous Message | Tom Lane | 2006-03-08 16:20:50 | Re: Merge algorithms for large numbers of "tapes" |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-03-08 16:29:55 | Re: Add switches for DELIMITER and NULL in pg_dump COPY |
| Previous Message | David Fetter | 2006-03-08 16:20:39 | Re: [PATCHES] Add switches for DELIMITER and NULL in pg_dump COPY |