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

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

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
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 --copy-null
Date: 2006-01-30 21:27:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
David Fetter wrote:
> On Thu, Jan 26, 2006 at 10:17:05PM -0500, Tom Lane wrote:
> > David Fetter <david(at)fetter(dot)org> writes:
> > > I have seed database scripts quasi-generated from pg_dump which
> > > include COPY statements, but the data is hard to edit (especially
> > > cut & paste operations) when the COPY delimiter is some
> > > non-visible character like \t.
> > 
> > This seems like an awfully weak use-case for adding to pg_dump's
> > already overly complicated feature set.
> Those who don't use it will never see it.

Documentation itself is providing the option to the user and they have
to decide if it is useful.  No visible feature has zero cost for our

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-01-30 21:31:29
Subject: Re: Logging statements and parameter values
Previous:From: Marc G. FournierDate: 2006-01-30 21:21:06
Subject: Re: Want to add to contrib.... xmldbx

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