From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: CSV mode option for pg_dump |
Date: | 2006-06-14 14:55:04 |
Message-ID: | 200606141455.k5EEt4i23644@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > As was stated before, the use-case for this is by people we don't
> > normally have contact with.
>
> Or who don't exist.
>
> Once again: give me a plausible use-case for pulling this data out of a
> pg_dump output file. You'd need data-massaging code anyway just to
> extract the data, so why not expect that code to convert to CSV or
> whatever other format you might want? If you can think of use-cases like
> this, why do you think the destination format is necessarily CSV and not
> something else? If it is something else, adding a CSV option to pg_dump
> makes it *harder* not easier to write that massaging code, because now
> it's got to cope with N dump formats not one.
I don't have to think of a use case. I trusted the people who said we
needed CSV, so I trust them again if they say doing pg_dump with CSV
would be a good idea.
Also, my suggestion of --copy-with would allow CSV and other format
modifications with minimal code and complexity.
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2006-06-14 14:59:36 | Re: postgresql and process titles |
Previous Message | Tom Lane | 2006-06-14 14:50:21 | Re: CSV mode option for pg_dump |