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>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: CSV mode option for pg_dump |
Date: | 2006-06-13 01:25:35 |
Message-ID: | 200606130125.k5D1PZ001508@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Already on TODO:
pg_dump:
o %Add CSV output format
---------------------------------------------------------------------------
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > Something someone said on IRC just now triggered a little memory ... I
> > think we should provide an option to have pg_dump work in CSV mode
> > rather than text mode. This probably doesn't have much importance in the
> > case of text dumps, but in custom or tar dumps where you might want to
> > get at individual data members, having an option for CSVs that you want
> > to load into some other product might be nice.
>
> This is silly. You'd just COPY the particular table you want, not use
> pg_dump. pg_dump's already got an unreasonably large number of options
> without adding ones that have essentially zero use. Also, I think there
> are sufficient grounds to worry about whether a CSV dump would always
> reload correctly --- we already know that that's a poorly thought out
> "standard".
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
--
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 | Bruno Wolff III | 2006-06-13 04:25:56 | Re: Ranges for well-ordered types |
Previous Message | Tom Lane | 2006-06-13 00:14:01 | Re: longjmp in psql considered harmful |