| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Chris Jewell <c(dot)jewell(at)lancaster(dot)ac(dot)uk> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Monitoring database for changes - backup purposes |
| Date: | 2005-10-14 19:24:54 |
| Message-ID: | 20051014192454.GS23883@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas F. O'Connell | 2005-10-14 20:49:29 | Re: postmaster blues after system restart |
| Previous Message | Chris Jewell | 2005-10-14 18:29:31 | Re: Monitoring database for changes - backup purposes |