Received: from BKMAIL.sixtyfootspider.com (sfs-pat.sixtyfootspider.com [216.52.187.112]) by hub.org (8.10.1/8.10.1) with ESMTP id e7OHP7510104 for ; Thu, 24 Aug 2000 13:25:07 -0400 (EDT) Received: by BKMAIL.sixtyfootspider.com with Internet Mail Service (5.5.2650.21) id ; Thu, 24 Aug 2000 12:16:53 -0500 Message-ID: <01CCE949D2717845BA2E573DC081167E052E8F@BKMAIL.sixtyfootspider.com> From: "Ingram, Bryan" To: "'pgsql-sql@postgresql.org'" Subject: Is there a way to tell if db has changed? Date: Thu, 24 Aug 2000 12:16:49 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Archive-Number: 200008/264 > 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 >