Tom Lane wrote:
Bruce Momjian <pgman@candle.pha.pa.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. +

Search Discussions

Discussion Posts


Follow ups

Related Discussions



site design / logo © 2019 Grokbase