From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(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:31:39 |
Message-ID: | 23711.1150295499@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I agree with Andrew. If there are bugs in CSV, then we should fix them,
> not avoid give users this usability improvement.
The case for it being a usability improvement seems very weak to me;
no one has yet demonstrated an actual use-case where someone would pull
CSV data out of pg_dump output instead of just dumping the table
directly with COPY. Now the "anti" case is admittedly hypothetical:
I'm supposing that we will eventually be bitten by portability problems
with CSV-style dumps not being loadable into future versions. But given
the weak nature of the "pro" case, I think we should be conservative
and not take that risk.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | letizia leo | 2006-06-14 14:35:14 | Tuple hint bits (INFOMASK) upon transaction abort |
Previous Message | Bruce Momjian | 2006-06-14 13:18:31 | Re: [PATCHES] PL/pgSQL: SELECT INTO EXACT |