| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] Patch for pg_dump: Multiple -t options and |
| Date: | 2004-08-13 03:37:38 |
| Message-ID: | 411C3782.3040406@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Christopher Kings-Lynne wrote:
> OK, everything for pg_dump TODO I can think of:
>
> [snip]
> * Export to other database (eg. Oracle, MySQL and DB2) formats
>
>
This strikes me as a can of worms, or to mix metaphors a bit, a rathole
from which we might never emerge.
I did have a thought the other day - now that we have COPY in/out
talking CSV format, it might be nice to have an option on pg_dump to use
CSV format rather than our own native text format.
That should make exporting to other DBs a lot easier. Of course, that
could be cutting our own throat too ...
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-08-13 04:01:40 | Re: DROP TABLESPACE causes panic during recovery |
| Previous Message | Christopher Kings-Lynne | 2004-08-13 03:16:14 | Re: [PATCHES] Patch for pg_dump: Multiple -t options and |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2004-08-13 03:38:55 | Add GUC_REPORT to server_encoding, integer_datetimes |
| Previous Message | Christopher Kings-Lynne | 2004-08-13 03:16:14 | Re: [PATCHES] Patch for pg_dump: Multiple -t options and |