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

From Darcy Buskermolen
Subject Re: Monitoring database for changes - backup purposes
Date
Msg-id 200510141059.39852.darcy@wavefire.com
Whole thread Raw
In response to Monitoring database for changes - backup purposes  (Chris Jewell <c.jewell@lancaster.ac.uk>)
Responses Re: Monitoring database for changes - backup purposes  (Chris Jewell <c.jewell@lancaster.ac.uk>)
List pgsql-admin
On Friday 14 October 2005 06:19, Chris Jewell wrote:
> Hi,
>
> I have a query about a backup policy that I wish to implement.
> Currently, we are running a PostgreSQL server with a very large database
> on it.  The database consists of a core of read-only tables, with tables
> created by the users going by default into the user's own schemas.  For
> backup purposes, I have a script that uses pg_dump to create dumps of
> the individual user schemas.  However, this is mainly a read-only
> database and information is added or updated only rarely.  What I really
> need is a method of monitoring the database, such that my backup script
> will only back any one schema up if it has changed since it was last
> backed up.  Is there any way to do this?  Is there a checksum function
> or something that I could use?

No there is not, but would a diff -q be sufficient for your needs ?


>
> Thanks,
>
> Chris

--
Darcy Buskermolen
Wavefire Technologies Corp.

http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759

pgsql-admin by date:

Previous
From: "Andy"
Date:
Subject: Postgres: writer process !? Time of process not to long???
Next
From: Chris Jewell
Date:
Subject: Re: Monitoring database for changes - backup purposes