This is a discussion on Re: pg_dump additional options for performance within the pgsql Hackers forums, part of the PostgreSQL category; --> Added to TODO: o Allow pre/data/post files when dumping a single object, for performance reasons http://archives.postgresql.org/pgsql...2/msg00205.php --------------------------------------------------------------------------- Simon Riggs ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Added to TODO: o Allow pre/data/post files when dumping a single object, for performance reasons http://archives.postgresql.org/pgsql...2/msg00205.php --------------------------------------------------------------------------- Simon Riggs wrote: > pg_dump allows you to specify -s --schema-only, or -a --data-only. > > The -s option creates the table, as well as creating constraints and > indexes. These objects need to be dropped prior to loading, if we are to > follow the performance recommendations in the docs. But the only way to > do that is to manually edit the script to produce a cut down script. > > So it would be good if we could dump objects in 3 groups > 1. all commands required to re-create table > 2. data > 3. all commands required to complete table after data load > > My proposal is to provide two additional modes: > --schema-pre-load corresponding to (1) above > --schema-post-load corresponding to (3) above > > This would then allow this sequence of commands > > pg_dump --schema-pre-load > pg_dump --data-only > pg_dump --schema-post-load > > to be logically equivalent, but faster than > > pg_dump --schema-only > pg_dump --data-only > > both forms of which are equivalent to just > > pg_dump > > > [Assuming data isn't changing between invocations...] > > -- > Simon Riggs > 2ndQuadrant http://www.2ndQuadrant.com > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |
| |||
| Bruce Momjian wrote: > > Added to TODO: > > o Allow pre/data/post files when dumping a single object, for > performance reasons > > http://archives.postgresql.org/pgsql...2/msg00205.php "When dumping a single object"?? Do you mean database? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support - Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |
| ||||
| Alvaro Herrera wrote: > Bruce Momjian wrote: > > > > Added to TODO: > > > > o Allow pre/data/post files when dumping a single object, for > > performance reasons > > > > http://archives.postgresql.org/pgsql...2/msg00205.php > > "When dumping a single object"?? Do you mean database? I have updated the wording: o Allow pre/data/post files when schema and data are dumped separately, for performance reasons -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + - Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |