Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 9CFC79FA433 for ; Wed, 15 Nov 2006 12:06:53 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 08652-05 for ; Wed, 15 Nov 2006 12:06:46 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from perth.mailnetwork.co.uk (perth.mailnetwork.co.uk [80.175.28.46]) by postgresql.org (Postfix) with ESMTP id 526089F9CF9 for ; Wed, 15 Nov 2006 12:06:45 -0400 (AST) Received: from [213.146.143.243] (port=2151 helo=[172.16.208.165]) by perth.mailnetwork.co.uk with esmtpa (Exim 4.63) (envelope-from ) id 1GkNHi-0001KA-Dv; Wed, 15 Nov 2006 16:06:46 +0000 Message-ID: <455B3B90.1030005@mailnetwork.co.uk> Date: Wed, 15 Nov 2006 16:08:48 +0000 From: "Andy Shellam (Mailing Lists)" User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Simon Riggs CC: pgsql-admin@postgresql.org Subject: Re: Checkpoint Location Format References: <45508655.4040708@mailnetwork.co.uk> <1163542492.27956.116.camel@silverbirch.site> In-Reply-To: <1163542492.27956.116.camel@silverbirch.site> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/154 X-Sequence-Number: 23681 Yup that sounds useful - would this be another column added to the pg_stop_backup called "wal_filename" or similar? My script uses this name to find the date/time of the current ".backup" file and remove any files earlier than it (except obviously the one listed in the START WAL LOCATION). I've yet to run a restore test, but the backup and automatic archive clearout is working nicely. I'm not too worried about the SQL function to find the current WAL file, although I can see this could be useful too. Thanks, Andy. Simon Riggs wrote: > On Tue, 2006-11-07 at 13:12 +0000, Andy Shellam (Mailing Lists) wrote: > > >> I'm writing an automated file-system level backup application for use >> with WAL archiving, that will issue the pg_start_backup call, tar and >> gzip the cluster data directory, issue the pg_stop_backup call, and >> remove all previous un-needed WAL files from the archive. >> > > Is this any help? > > http://archives.postgresql.org/pgsql-patches/2006-05/msg00229.php > > If so, I'll see about updating it so it can get backpatched to 8.0 and > 8.1 also. > > -- Andy Shellam NetServe Support Team the Mail Network "an alternative in a standardised world" p: +44 (0) 121 288 0832/0839 m: +44 (0) 7818 000834