Re: pg_dump additional options for performance
От | Bruce Momjian |
---|---|
Тема | Re: pg_dump additional options for performance |
Дата | |
Msg-id | 200803230032.m2N0WKh19121@momjian.us обсуждение исходный текст |
Ответ на | pg_dump additional options for performance (Simon Riggs <simon@2ndquadrant.com>) |
Ответы |
Re: pg_dump additional options for performance
|
Список | pgsql-hackers |
Added to TODO: o Allow pre/data/post files when dumping a single object, for performance reasons http://archives.postgresql.org/pgsql-hackers/2008-02/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. +
В списке pgsql-hackers по дате отправления: