From: Simon Riggs <simon@2ndquadrant.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Luke Lonergan <LLonergan@greenplum.com>
Cc: David Lang <dlang@invendra.net>
Cc: Steve Oualline <soualline@stbernard.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Database restore speed
Date: Sat, 03 Dec 2005 12:38:48 +0000
Message-ID: <1133613528.2906.731.camel@localhost.localdomain> (raw)
In-Reply-To: <20051202201847.GE6026@ns.snowman.net>
References: <3E37B936B592014B978C4415F90D662D01C48F01@MI8NYCMAIL06.Mi8.com>
<20051202201847.GE6026@ns.snowman.net>
On Fri, 2005-12-02 at 15:18 -0500, Stephen Frost wrote:
> The other thought, of course, is that you could use PITR for your
> backups instead of pgdump...
Yes, it is much faster that way.
Over on -hackers a few optimizations of COPY have been discussed; one of
those is to optimize COPY when it is loading into a table created within
the same transaction as the COPY. This would allow pg_dumps to be
restored much faster, since no WAL need be written in this case.
I hope to work on this fairly soon.
Dumping/restoring data with pg_dump has wider uses than data protecting
backup.
Best Regards, Simon Riggs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: simon@2ndquadrant.com, sfrost@snowman.net, LLonergan@greenplum.com, dlang@invendra.net, soualline@stbernard.com
Subject: Re: Database restore speed
In-Reply-To: <1133613528.2906.731.camel@localhost.localdomain>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox