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 B69919DC84E for ; Fri, 23 Dec 2005 00:40:44 -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 32521-10 for ; Fri, 23 Dec 2005 00:40:43 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 362789DC83E for ; Fri, 23 Dec 2005 00:40:42 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jBN4ebn2015886; Thu, 22 Dec 2005 23:40:37 -0500 (EST) To: Stephen Frost cc: Mike C , Simon Riggs , pgsql-admin@postgresql.org Subject: Re: WAL and pg_dump In-reply-to: <20051223015001.GD6026@ns.snowman.net> References: <1135208028.2964.329.camel@localhost.localdomain> <1135289852.2964.542.camel@localhost.localdomain> <20051223015001.GD6026@ns.snowman.net> Comments: In-reply-to Stephen Frost message dated "Thu, 22 Dec 2005 20:50:01 -0500" Date: Thu, 22 Dec 2005 23:40:37 -0500 Message-ID: <15885.1135312837@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.038 required=5 tests=[AWL=0.038] X-Spam-Score: 0.038 X-Spam-Level: X-Archive-Number: 200512/290 X-Sequence-Number: 20010 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. 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? regards, tom lane