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

From Bruce Momjian
Subject Re: [PATCHES] Patch for pg_dump: Multiple -t options and
Date
Msg-id 200408180319.i7I3Jfu29730@candle.pha.pa.us
Whole thread Raw
In response to Re: [PATCHES] Patch for pg_dump: Multiple -t options and  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
OK, I have added a new pg_dump TODO section with adjustments based on
feedback from original list:

* pg_dump       o Allow pg_dumpall to use non-text output formats       o Have pg_dump use multi-statement transactions
forINSERT dumps       o -Allow pg_dump to dump CREATE CONVERSION (Christopher)       o -Make pg_restore continue after
errors,so it acts more like pg_dump         scripts       o Allow pg_dump to use multiple -t and -n switches
 
         This should be done by allowing a '-t schema.table' syntax.
       o Add dumping of comments on composite type columns       o Add dumping of comments on index columns       o
Replacecrude DELETE FROM method of pg_dumpall for cleaning of         users and groups with separate DROP commands
o Add dumping and restoring of LOB comments       o Stop dumping CASCADE on DROP TYPE commands in clean mode       o
Addfull object name to the tag field.  eg. for operators we need         '=(integer, integer)', instead of just '='.
  o Add pg_dumpall custom format dumps. This is probably best done by         combining pg_dump and pg_dumpall into a
singlebinary       o Add CSV output format
 

---------------------------------------------------------------------------

Andrew Dunstan wrote:
> 
> 
> 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
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
>                http://archives.postgresql.org
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: stop the presses (Re: 7.4.4 packaged ...)
Next
From: Tom Lane
Date:
Subject: Re: [ADMIN] SRPM for 8.0.0 beta?