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
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
