Re: CSV mode option for pg_dump - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: CSV mode option for pg_dump
Date
Msg-id 200606130125.k5D1PZ001508@candle.pha.pa.us
Whole thread Raw
In response to Re: CSV mode option for pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Already on TODO:

pg_dump:
         o %Add CSV output format


---------------------------------------------------------------------------

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.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@postgresql.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. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: longjmp in psql considered harmful
Next
From: Bruno Wolff III
Date:
Subject: Re: Ranges for well-ordered types