Re: pg_dump additional options for performance - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump additional options for performance
Date
Msg-id 24991.1204004369@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump additional options for performance  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: pg_dump additional options for performance  (Simon Riggs <simon@2ndquadrant.com>)
Re: pg_dump additional options for performance  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> ... 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

[ much subsequent discussion snipped ]

BTW, what exactly was the use-case for this?  The recent discussions
about parallelizing pg_restore make it clear that the all-in-one
dump file format still has lots to recommend it.  So I'm just wondering
what the actual advantage of splitting the dump into multiple files
will be.  It clearly makes life more complicated; what are we buying?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: 8.3 / 8.2.6 restore comparison
Next
From: Jeff Davis
Date:
Subject: Re: 8.3 / 8.2.6 restore comparison