From: Ingram, Bryan <BIngram@sixtyfootspider.com>
To: 'pgsql-sql@postgresql.org' <pgsql-sql@postgresql.org>
Subject: Is there a way to tell if db has changed?
Date: Thu, 24 Aug 2000 12:16:49 -0500
Message-ID: <01CCE949D2717845BA2E573DC081167E052E8F@BKMAIL.sixtyfootspider.com> (raw)
> It would seem about that the only currently viable technique for creating
> a standby database in case of a primary database failure is to ship output
> from pg_dump(all) to an awaiting postgres instance and reload them.
>
> I'm currently working on a few scripts to accomplish this which use cron
> to schedule the backup which then gets shipped and reloaded.
>
> This is not efficient since since the desired frequency of backups will
> often be greater than the frequency of data changes. However, I can't
> know when exactly a user will change data, so I was looking for a better
> way.
>
> Is there a way to determine if a particular database has changed, and
> therefore needs to be backed up?
>
>
> Thanks,
> Bryan
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: BIngram@sixtyfootspider.com
Subject: Re: Is there a way to tell if db has changed?
In-Reply-To: <01CCE949D2717845BA2E573DC081167E052E8F@BKMAIL.sixtyfootspider.com>
References: <01CCE949D2717845BA2E573DC081167E052E8F@BKMAIL.sixtyfootspider.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox