Date: Tue, 16 Nov 1999 15:41:23 -0500
From: Richard Welsh <rwelsh@OneStepInternet.com>
Subject: Re: [GENERAL] Re: replication
To: pgsql-general@hub.org
Message-id: <008601bf3072$f2593200$6301a8c0@laptop.local>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit

Is it possible to log the transactions ( as complete statements ) on one
database then process the logged transactions on the second database at
intervals to keep it up to date?

RDW.

-----Original Message-----
From: Jeff Hoffmann <jeff@propertykey.com>
To: Aaron J. Seigo <aaron@gtv.ca>; pgsql-general@hub.org
<pgsql-general@hub.org>
Date: November 16, 1999 2:28 PM
Subject: Re: [GENERAL] Re: replication


>"Aaron J. Seigo" wrote:
>
>> this needs to be in the back end... otherwise, if you have multiple
people
>> performing updates on different replicated servers, how can you guarentee
>> concurancy? how do you manage the differences between read-only and
updateable
>> replicants? (this can be done using your wrapper method, but quickly gets
>> clumsy)
>
>yeah it can get clumsy, but fortunately updates are pretty rare in my
>case (and usually only performed by one person) so i don't really worry
>about those issues, but i should.  the only safety issue i use is
>starting a transaction for each connection, perform the action on all of
>the databases, and then commit the transaction on each.  it's not bad
>unless one of the commits fails and the others don't, then i have to
>retry the failed ones & hope it works.  i don't know how to fix it if i
>had to give up on one of the transactions for a mirror.  again, not
>perfect, but it works pretty well for me & my simpler cases.
>
>************
>
>