From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] Patch for pg_dump: Multiple -t options and |
Date: | 2004-08-18 03:19:41 |
Message-ID: | 200408180319.i7I3Jfu29730@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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 for INSERT 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 Replace crude 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 Add full 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 single binary
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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-18 03:24:14 | Re: [HACKERS] SRPM for 8.0.0 beta? |
Previous Message | Tom Lane | 2004-08-18 03:12:29 | Re: stop the presses (Re: 7.4.4 packaged ...) |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-08-18 03:26:18 | Re: Add GUC_REPORT to server_encoding, integer_datetimes |
Previous Message | Bruce Momjian | 2004-08-18 03:06:35 | Re: Replace incorrect example for quote_ident |