Subject: Re: Home-brewed table syncronization
From: Cliff Wells <LogiplexSoftware@earthlink.net>
To: pgsql-sql@postgresql.org
In-Reply-To: <200307091414.19959.mike@nachbaur.com>
References: <200307091414.19959.mike@nachbaur.com>
Content-Type: text/plain
Organization: Logiplex Corporation
Message-Id: <1057786137.15508.29.camel@software1.logiplex.internal>
Mime-Version: 1.0
Date: 09 Jul 2003 14:28:57 -0700
Content-Transfer-Encoding: 7bit

On Wed, 2003-07-09 at 14:14, Michael A Nachbaur wrote:

> So, I'm looking at syncronizing 4 tables from one master database to several 
> child databases. I'm thinking of doing the following with DBD::Multiplex:
> 
> DELETE FROM TableA;
> INSERT INTO TableA (..) VALUES (...);
> ....
> 
> on all the child databases, but I'm not sure what kind of impact this would 
> have on my servers.  My impression is that this would hammer the indexes, and 
> might blow any memory optimization out the window.  Only a few records in my 
> dataset will change from time-to-time, but just the process of determining 
> what is different may take more effort than simply rebuilding.

Keep a timestamp associated with each record.  Only update the records
with timestamps later than your last sync.

-- 
Cliff Wells, Software Engineer
Logiplex Corporation (www.logiplex.net)
(503) 978-6726  (800) 735-0555