| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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 22:26:50 |
| Message-ID: | 44908D2A.7000208@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
>
> 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 just noticed that the data members all have \. and some blank lines at
the end, so wash that out.
We now return you to normal -hacking
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-14 22:31:17 | Re: libpq's pollution of application namespace |
| Previous Message | Josh Berkus | 2006-06-14 22:26:45 | Re: Multi-byte and client side character encoding |