Re: pg_dump additional options for performance

From: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Dunstan <pgsql(at)tomd(dot)cc>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: pg_dump additional options for performance
Date: 2008-02-26 14:27:46
Message-ID: 47C421E2.50209@cheapcomplexdevices.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander wrote:
> On Tue, Feb 26, 2008 at 08:28:11AM -0500, Andrew Dunstan wrote:
>> Simon Riggs wrote:
>>> Separate files seems much simpler...
>> Yes, We need to stick to the KISS principle.
>> ISTM that we could simply invent a new archive format of "d" for directory.
> Yeah, you can always ZIP (or whatever) the resulting directory when you're
> done..

I could imagine this being very rsync friendly too.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-02-26 14:46:38 Bulk loading performance improvements
Previous Message Simon Riggs 2008-02-26 14:27:07 Re: pg_dump additional options for performance