Re: [PATCHES] Patch for pg_dump: Multiple -t options and - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [PATCHES] Patch for pg_dump: Multiple -t options and
Date
Msg-id 411C3782.3040406@dunslane.net
Whole thread Raw
In response to Re: [PATCHES] Patch for pg_dump: Multiple -t options and new -T option  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: [PATCHES] Patch for pg_dump: Multiple -t options and  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Re: [PATCHES] Patch for pg_dump: Multiple -t options and  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers

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


pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: [PATCHES] Patch for pg_dump: Multiple -t options and
Next
From: Bruce Momjian
Date:
Subject: Re: DROP TABLESPACE causes panic during recovery