Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id D2F349F970A for ; Fri, 2 Nov 2007 02:44:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 56337-05 for ; Fri, 2 Nov 2007 02:44:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from s-utl02-atpop.stsn.net (s-utl02-atpop.stsn.net [72.254.128.202]) by postgresql.org (Postfix) with SMTP id 770DB9F9460 for ; Fri, 2 Nov 2007 02:44:05 -0300 (ADT) Received: from s-utl02-atpop.stsn.net ([127.0.0.1]) by s-utl02-atpop.stsn.net (SMSSMTP 4.1.2.20) with SMTP id M2007110201440408648 for ; Fri, 02 Nov 2007 01:44:04 -0400 Received: from [10.4.153.241] ([10.4.153.241]) by s-utl02-atpop.stsn.net for pgsql-admin@postgresql.org; Fri, 2 Nov 2007 01:44:04 -0400 From: Kevin Kempter To: pgsql-admin@postgresql.org Subject: Re: Understanding wal segments Date: Thu, 1 Nov 2007 23:38:13 -0600 User-Agent: KMail/1.9.7 References: <200711012155.16409.kevin@kevinkempterllc.com> <200711012239.07980.kevin@kevinkempterllc.com> <22325.1193981928@sss.pgh.pa.us> In-Reply-To: <22325.1193981928@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711012338.13229.kevin@kevinkempterllc.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.478 tagged_above=0 required=5 tests=AWL=-0.467, BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13 X-Spam-Level: X-Archive-Number: 200711/15 X-Sequence-Number: 27258 On Thursday 01 November 2007 23:38:48 Tom Lane wrote: > Kevin Kempter writes: > > Also I suspect after each filesystem backup I should remove the older > > archived segments since the file system backup makes them > > irrelevant. Is this accurate? > > Depends what your goals are. If you only want to be able to recover > the latest database state then you only need archived WAL segments > back to the start of the latest filesystem backup. If you are > interested in the "PITR" aspect of it --- being able to revert back > to last Tuesday before some bad guy injected bad data, say --- then > you'll want to keep older filesystem backups too, and a continuous > string of archived WAL files covering the period of interest. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster Makes sense. Thanks. One more question. I see a fair amount of file changed warnings in the tar output. Like this: tar: ./data/base/82097725/4242350944: file changed as we read it ./data/base/82097725/143763179 ./data/base/82097725/3587685114 ./data/base/82097725/3587684991 ./data/base/82097725/3587685046 ./data/base/82097725/3587685003 ./data/base/82097725/3588484372 tar: ./data/base/82097725/3588484372: file changed as we read it ./data/base/82097725/3587685172 ./data/base/82097725/10733 ./data/base/82097725/3588482971 ./data/base/82097725/4082992388 ./data/base/82097725/4242349291.4 tar: ./data/base/82097725/4242349291.4: file changed as we read it Is this an issue or does postgres comensate for this since it knows I'm running a backup (i've run a pg_start_backup) ? Thx /Kevin