From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(at)postgresql(dot)org> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Use a latch to make startup process wake up and replay |
Date: | 2010-09-15 11:14:33 |
Message-ID: | AANLkTin-Gm9MB3N1T=CgyQ+BbY9Dx=u3-OUuietwvARN@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Wed, Sep 15, 2010 at 7:35 PM, Heikki Linnakangas
<heikki(at)postgresql(dot)org> wrote:
> Log Message:
> -----------
> Use a latch to make startup process wake up and replay immediately when
> new WAL arrives via streaming replication. This reduces the latency, and
> also allows us to use a longer polling interval, which is good for energy
> efficiency.
>
> We still need to poll to check for the appearance of a trigger file, but
> the interval is now 5 seconds (instead of 100ms), like when waiting for
> a new WAL segment to appear in WAL archive.
Good work!
+ /*
+ * Take ownership of the wakup latch if we're going to sleep during
+ * recovery.
+ */
I found a typo: s/wakup/wakeup/
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-09-15 11:48:44 | Re: pgsql: Use a latch to make startup process wake up and replay |
Previous Message | Heikki Linnakangas | 2010-09-15 10:35:05 | pgsql: Use a latch to make startup process wake up and replay |
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-09-15 11:48:44 | Re: pgsql: Use a latch to make startup process wake up and replay |
Previous Message | Heikki Linnakangas | 2010-09-15 10:35:05 | pgsql: Use a latch to make startup process wake up and replay |