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
On Tue, 2006-11-07 at 13:12 +, 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 a
Hi Jim,
Tom did answer actually! (Although it was first thing in the morning
and he hadn't had any caffeine so he may have forgot to copy the list in
;) )
I forget what he said the format was now, and I haven't got his e-mail,
but I've just done a regex to match one or more characters before
On Tue, Nov 07, 2006 at 01:12:53PM +, Andy Shellam (Mailing Lists) wrote:
> Hi,
>
> 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,
Hi,
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.
I need to write a regu
