From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: CSV mode option for pg_dump |
Date: | 2006-06-14 15:13:08 |
Message-ID: | 44902784.5040301@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
>As was stated before, the use-case for this is by people we don't
>normally have contact with.
>
>
>
I do think we need a use case for what we do.
The main use case seems to me to be where you are exporting a whole
database or most of it with a very large number of tables, and it is
convenient to have all the CSVs created for you rather than have to make
them manually one at a time. You could get these out of, say, a tar
format dump very easily.
I said near the beginning of this that a pgfoundry project to create a
tool for this might be an alternative way to go. If that's the consensus
then Ok. I just bristle a bit at the suggestion that we might not get
back what we started with from a CSV dump, because we can, AFAIK.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-06-14 15:55:54 | Re: CSV mode option for pg_dump |
Previous Message | Greg Stark | 2006-06-14 15:09:35 | Re: CSV mode option for pg_dump |