X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 1AC4E9DC808 for ; Fri, 23 Dec 2005 09:42:59 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 73577-02 for ; Fri, 23 Dec 2005 09:43:01 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from ns.snowman.net (ns.snowman.net [66.92.160.21]) by postgresql.org (Postfix) with ESMTP id 51CC59DC80B for ; Fri, 23 Dec 2005 09:42:56 -0400 (AST) Received: by ns.snowman.net (Postfix, from userid 1000) id 6DD2217B08; Fri, 23 Dec 2005 08:43:47 -0500 (EST) Date: Fri, 23 Dec 2005 08:43:47 -0500 From: Stephen Frost To: Tom Lane Cc: Mike C , Simon Riggs , pgsql-admin@postgresql.org Subject: Re: WAL and pg_dump Message-ID: <20051223134347.GE6026@ns.snowman.net> Mail-Followup-To: Tom Lane , Mike C , Simon Riggs , pgsql-admin@postgresql.org References: <1135208028.2964.329.camel@localhost.localdomain> <1135289852.2964.542.camel@localhost.localdomain> <20051223015001.GD6026@ns.snowman.net> <15885.1135312837@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/biQ4R/HlpZA3B3Q" Content-Disposition: inline In-Reply-To: <15885.1135312837@sss.pgh.pa.us> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.4.24ns.3.0 (i686) X-Uptime: 08:40:36 up 195 days, 5:52, 11 users, load average: 0.29, 0.16, 0.06 User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.086 required=5 tests=[AWL=0.086] X-Spam-Score: 0.086 X-Spam-Level: X-Archive-Number: 200512/299 X-Sequence-Number: 20019 --/biQ4R/HlpZA3B3Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Tom Lane (tgl@sss.pgh.pa.us) wrote: > Stephen Frost 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. >=20 > 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 --/biQ4R/HlpZA3B3Q Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDq/8TrzgMPqB3kigRAir7AJ9UubDhloS3otkzaSN+xqS9VV1HpwCfZbXQ cM6/Bt/wIeIt5P4YltHHubE= =dYkr -----END PGP SIGNATURE----- --/biQ4R/HlpZA3B3Q--