Re: Monitoring database for changes - backup purposes - Mailing list pgsql-admin

From Jim C. Nasby
Subject Re: Monitoring database for changes - backup purposes
Date
Msg-id 20051014192454.GS23883@pervasive.com
Whole thread Raw
In response to Re: Monitoring database for changes - backup purposes  (Chris Jewell <c.jewell@lancaster.ac.uk>)
List pgsql-admin
On Fri, Oct 14, 2005 at 07:29:31PM +0100, Chris Jewell wrote:
> Hi,
>
> Yes, diff would work and is my current plan, but it requires me to
> perform the backup first.  What I needed really was a system by which a
> backup would only be run if there was something that needed backing up.

I believe he meant diffing the files that store the tables.

Another possibility that I think would work would be checking the
last-modified timestamp of all the files in a schema. Though the easiest
way to do that is probably to build a list of any files that have
changed since the last backup and then figure out what schemas they're
in.
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-admin by date:

Previous
From: Chris Jewell
Date:
Subject: Re: Monitoring database for changes - backup purposes
Next
From: "Thomas F. O'Connell"
Date:
Subject: Re: postmaster blues after system restart