From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: pg_dump additional options for performance |
Date: | 2008-07-28 02:40:25 |
Message-ID: | 488D3199.2040902@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Stephen Frost wrote:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> Stephen Frost <sfrost(at)snowman(dot)net> writes:
>>> I dislike, and doubt that I'd use, this approach. At the end of the
>>> day, it ends up processing the same (very large amount of data) multiple
>>> times.
> This would depend on the dump being in the custom format, though I
> suppose that ends up being true for any usage of these options. I've
> never really been a fan of the custom format, in large part because it
> doesn't really buy you all that much and makes changing things more
> difficult (by having to extract out what you want to change, and then
> omit it from the restore).
Custom format rocks for partial set restores from a whole dump. See the
TOC option :)
Joshua D. Drake
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2008-07-28 02:50:18 | Re: pg_dump additional options for performance |
Previous Message | daveg | 2008-07-28 01:32:59 | Re: [PATCHES] pg_dump additional options for performance |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2008-07-28 02:50:18 | Re: pg_dump additional options for performance |
Previous Message | daveg | 2008-07-28 01:32:59 | Re: [PATCHES] pg_dump additional options for performance |