From: | Darcy Buskermolen <darcy(at)wavefire(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Monitoring database for changes - backup purposes |
Date: | 2005-10-14 17:59:39 |
Message-ID: | 200510141059.39852.darcy@wavefire.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Jewell | 2005-10-14 18:29:31 | Re: Monitoring database for changes - backup purposes |
Previous Message | Arnau Rebassa Villalonga | 2005-10-14 14:56:27 | Re: help with pg_dump timings |