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

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

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: new pg_dump options --copy-delimiter and
Date: 2006-01-27 15:18:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> Those who don't use it will never see it.
It does however add more maintenance to the code.

>> Furthermore, it's quite unclear why you'd use pg_dump at all to
>> generate a data file that you intend to feed to some other program.
> In my case, it's about being copy/paste friendly.
David I don't get this... what are you copying from/to that would
wouldn't just script? If you throw into a script you can change
the delimiter on the fly using translation.

> Actually, it's not.  I'm attaching my preliminary patch, as I see I
> haven't explained it well enough.
Perhaps a test case that shows the productivity of it? I am not
arguing whether or not this is a useful feature but I don't
see the purpose.


Joshua D. Drake

> Cheers,
> D

The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PLphp, PLperl -

In response to


pgsql-hackers by date

Next:From: Jason EssingtonDate: 2006-01-27 15:21:23
Subject: Re: Segfault Exiting psql
Previous:From: Tom LaneDate: 2006-01-27 15:09:00
Subject: Re: Adding a --quiet option to initdb

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