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 95CDA9DC837 for ; Thu, 22 Dec 2005 21:49:15 -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 03873-07 for ; Thu, 22 Dec 2005 21:49:18 -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 B7C359DC807 for ; Thu, 22 Dec 2005 21:49:12 -0400 (AST) Received: by ns.snowman.net (Postfix, from userid 1000) id A94B417AE2; Thu, 22 Dec 2005 20:50:01 -0500 (EST) Date: Thu, 22 Dec 2005 20:50:01 -0500 From: Stephen Frost To: Mike C Cc: Simon Riggs , pgsql-admin@postgresql.org Subject: Re: WAL and pg_dump Message-ID: <20051223015001.GD6026@ns.snowman.net> Mail-Followup-To: Mike C , Simon Riggs , pgsql-admin@postgresql.org References: <1135208028.2964.329.camel@localhost.localdomain> <1135289852.2964.542.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="j6/KplwdquksNt50" Content-Disposition: inline In-Reply-To: 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: 20:39:13 up 194 days, 17:50, 11 users, load average: 0.19, 0.09, 0.02 User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.08 required=5 tests=[AWL=0.080] X-Spam-Score: 0.08 X-Spam-Level: X-Archive-Number: 200512/287 X-Sequence-Number: 20007 --j6/KplwdquksNt50 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Mike C (smith.not.western@gmail.com) wrote: > Yes, space is our limiting factor. A pg_dump archive format backup takes > about 40mins for 25GB. A restore IIRC takes about 2 hours. However the si= ze > of the database is expected to grow to about 120 GB within a few months a= nd > by the end of 2006 over 400 GB. The current capacity of our DS 400 SAN is > 600 GB. at 400GB my only backup option with the existing hardware is > pg_dump. However I suspect now that I really should be looking at additio= nal > hardware. Yeah, that pg_dump restore time is pretty rough. As I recall, the initial backup of our 360GB (or so) database took=20 about 6 hours and the restore only took about 2 hours. One nice thing (well, in a way I guess) was that the whole thing compressed down to under 100GB. This was on an IBM DS4600 SAN (iirc, something along those=20 lines) with 5 320GB FC disks in a RAID-5. I'm not really looking forward to the day I get to pg_dump and pg_restore the whole thing to move to 8.1. :) Thanks, Stephen --j6/KplwdquksNt50 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) iD8DBQFDq1fJrzgMPqB3kigRAopGAKCc1yyFROEU0NZycOBOOfO+enC+OwCfeXrV JjGNglZf2UNEV6ETexHxPEI= =o6d5 -----END PGP SIGNATURE----- --j6/KplwdquksNt50--