| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Boszormenyi Zoltan <zb(at)cybertec(dot)at>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Hans-Juergen Schoenig <hs(at)cybertec(dot)at> |
| Subject: | Re: Synchronous replication patch built on SR |
| Date: | 2010-05-18 20:03:38 |
| Message-ID: | 4BF2F29A.4030004@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18/05/10 07:41, Fujii Masao wrote:
> On Sat, May 15, 2010 at 4:59 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> BTW, What I'd like to see as a very first patch first is to change the
>> current poll loops in walreceiver and walsender to, well, not poll.
>> That's a requirement for synchronous replication, is very useful on its
>> own, and requires a some design and implementation effort to get right.
>> It would be nice to get that out of the way before/during we discuss the
>> more user-visible behavior.
>
> Yeah, we should wake up the walesender from sleep to send WAL data
> as soon as it's flushed. But why do we need to change the loop of
> walreceiver? Or you mean changing the poll loop in the startup process?
Yeah, changing the poll loop in the startup process is what I meant.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-05-18 20:17:51 | Re: pg_upgrade - link mode and transaction-wraparound data loss |
| Previous Message | Bruce Momjian | 2010-05-18 19:56:48 | Re: pg_upgrade - link mode and transaction-wraparound data loss |