From: Stephen Frost <sfrost@snowman.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Mike C <smith.not.western@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL and pg_dump
Date: Fri, 23 Dec 2005 08:43:47 -0500
Message-ID: <20051223134347.GE6026@ns.snowman.net> (raw)
In-Reply-To: <15885.1135312837@sss.pgh.pa.us>
References: <bd0eabd0512121418h4c39a3e6mc71947264e18656f@mail.gmail.com>
<1135208028.2964.329.camel@localhost.localdomain>
<bd0eabd0512221309r5bcb41e2s69e9a7fdc8cb9edb@mail.gmail.com>
<1135289852.2964.542.camel@localhost.localdomain>
<bd0eabd0512221734v3d474ba1o8a8b9bfd3ebbdf24@mail.gmail.com>
<20051223015001.GD6026@ns.snowman.net>
<15885.1135312837@sss.pgh.pa.us>
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> Stephen Frost <sfrost@snowman.net> writes:
> > As I recall, the initial backup of our 360GB (or so) database took
> > about 6 hours and the restore only took about 2 hours.
>
> Really? I'd certainly have guessed the opposite (mainly because of
> index build time, constraint checking, etc during reload). Could it
> be that compression of the pg_dump output is swamping all else during
> the backup phase?
Sorry, I thought I was being clear (guess not)- I wasn't talking about
using pg_dump but rather PITR and tar/untar. I was trying to point out
that using PITR and tar/untar can be much, much, much nicer when you
have lots and lots of data to deal with (like a data warehouse would
have...). Of course, I can also do snapshots with the SAN, but that's a
one-time thing unlike PITR where you can choose any point in time to
recover to.
Thanks,
Stephen
Attachments:
signature.asc (application/pgp-signature, 188B) download
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: sfrost@snowman.net, tgl@sss.pgh.pa.us, smith.not.western@gmail.com, simon@2ndquadrant.com
Subject: Re: WAL and pg_dump
In-Reply-To: <20051223134347.GE6026@ns.snowman.net>
References: <bd0eabd0512121418h4c39a3e6mc71947264e18656f@mail.gmail.com> <1135208028.2964.329.camel@localhost.localdomain> <bd0eabd0512221309r5bcb41e2s69e9a7fdc8cb9edb@mail.gmail.com> <1135289852.2964.542.camel@localhost.localdomain> <bd0eabd0512221734v3d474ba1o8a8b9bfd3ebbdf24@mail.gmail.com> <20051223015001.GD6026@ns.snowman.net> <15885.1135312837@sss.pgh.pa.us> <20051223134347.GE6026@ns.snowman.net>
* 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