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 C3CCC9DC808 for ; Fri, 17 Feb 2006 10:55:37 -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 50850-03 for ; Fri, 17 Feb 2006 10:55:42 -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 899289DCB70 for ; Fri, 17 Feb 2006 10:55:35 -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 k1HEtbHb009252; Fri, 17 Feb 2006 09:55:37 -0500 (EST) To: andy.shellam@mailnetwork.co.uk cc: pgsql-admin@postgresql.org Subject: Re: WAL archive stopping too early In-reply-to: <43F59A88.1030504@mailnetwork.co.uk> References: <43F59A88.1030504@mailnetwork.co.uk> Comments: In-reply-to Andy Shellam message dated "Fri, 17 Feb 2006 09:42:32 +0000" Date: Fri, 17 Feb 2006 09:55:37 -0500 Message-ID: <9251.1140188137@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.11 required=5 tests=[AWL=0.110] X-Spam-Score: 0.11 X-Spam-Level: X-Archive-Number: 200602/214 X-Sequence-Number: 20635 Andy Shellam writes: > Note there are plenty more files ready to run in the archive, and the > contents of the backup label only mention 1A as the final WAL file of > the backup, so it is starting to read the next WAL file, but stopping > for some reason. Is it because of the "record with zero length" that's > causing it to fail? Yes --- that indicates the end of archive. It sounds to me like file 1B was archived while still only partly filled. Check the process you're using for deciding when to copy WAL files. > Also why is it restoring 1B from the archive twice? I think that's expected behavior --- it has something to do with wanting to make the copy of 1B into the new writable front WAL segment. You can dig through xlog.c if you want the details. regards, tom lane