Re: Synchronous Log Shipping Replication - Mailing list pgsql-hackers

From ITAGAKI Takahiro
Subject Re: Synchronous Log Shipping Replication
Date
Msg-id 20080909192040.7BF8.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: Synchronous Log Shipping Replication  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Synchronous Log Shipping Replication  (Markus Wanner <markus@bluegap.ch>)
Re: Synchronous Log Shipping Replication  (Markus Wanner <markus@bluegap.ch>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:

> The tricky part is, how does A know if it should wait, and for how long? 
> commit_delay sure isn't ideal, but AFAICS the log shipping proposal 
> doesn't provide any solution to that.

They have no relation each other directly,
but they need similar synchronization modules.

In log shipping, backends need to wait for WAL Sender's job,
and should wake up as fast as possible after the job is done.
It is similar to requirement of the group commit.

Signals and locking, borrewed from Postgres-R, are now studied
for the purpose in the log shipping, but I'm not sure it can be
also used in the group commit.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Our CLUSTER implementation is pessimal
Next
From: "Brendan Jurd"
Date:
Subject: Re: [PATCHES] to_date() validation