| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, fazool mein <fazoolmein(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, ganesh(at)vmware(dot)com |
| Subject: | Re: Synchronous replication - patch status inquiry |
| Date: | 2010-09-15 09:58:54 |
| Message-ID: | AANLkTik2A1o0tB4-RAxMZU+Md0EY5cgU_hpJjE+ixxch@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 15, 2010 at 6:38 AM, David Fetter <david(at)fetter(dot)org> wrote:
> Now that the latch patch is in, when do you think you'll be able to use it
> instead of the poll loop?
Here is the updated version, which uses a latch in communication from
walsender to backend. I've not changed the others. Because walsender
already uses it in HEAD, and Heikki already proposed the patch which
replaced the poll loop between walreceiver and startup process with
a latch.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| Attachment | Content-Type | Size |
|---|---|---|
| synchrep_0915.patch | application/octet-stream | 81.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-09-15 10:35:05 | pgsql: Use a latch to make startup process wake up and replay |
| Previous Message | Heikki Linnakangas | 2010-09-15 08:54:32 | Re: Sync Replication with transaction-controlled durability |