Hi,
Chris Browne wrote:
The approach that was going to be taken, in Slony-II, to apply locks
as early as possible so as to find conflicts as soon as possible,
rather than waiting, seems "eager" to me.
Agreed. WRT locking, one might also call it "pessimistic", but that
sounds so... negative.
[EMAIL PROTECTED] (Jan Wieck) writes:
> On 9/7/2007 11:01 AM, Markus Schiltknecht wrote:
>> None the less, Postgres-R is eager (or pessimistic?) in the sense
>> that it replicates *before* committing, so as to avoid
>> divergence. In [1] I've tried to make that distinction clear, and
>> I'm current
Hello Jan,
thank you for your feedback.
Jan Wieck wrote:
On 9/7/2007 11:01 AM, Markus Schiltknecht wrote:
This violates the common understanding of synchrony, because you can't
commit on a node A and then query another node B and expect it be
coherent immediately.
That's right. And there is
On 9/7/2007 11:01 AM, Markus Schiltknecht wrote:
Hi,
I'm asking for advice and hints regarding terms in database replication,
especially WRT Postgres-R. (Sorry for crossposting, but I fear not
reaching enough people on the Postgres-R ML alone)
I'm struggling on how to classify the Postgres-R
Hi,
I'm asking for advice and hints regarding terms in database replication,
especially WRT Postgres-R. (Sorry for crossposting, but I fear not
reaching enough people on the Postgres-R ML alone)
I'm struggling on how to classify the Postgres-R algorithm. Up until
recently, most people though
