hi...
> 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?
>
transaction logging is already done on disk in pg_log, however you can't count
on it being correct (es
PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
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 diffe
"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 y
hi...
> my favorite hack is to wrap the c/c++ api so you can set up a group of
> mirror database connections and then calling the wrapped functions will
> call the original function on each of the mirror database connections.
> i've really never thought of it as something that should be part of
