From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH 01/16] Overhaul walsender wakeup handling |
Date: | 2012-06-22 14:59:45 |
Message-ID: | CA+TgmobWdxEhm1Y4fPHPp-J3anayCEO5tzx7bk4KktdtwuzrLw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 22, 2012 at 10:45 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> > the likelihood of that as you know.
>> Hmm, well, I guess. I'm still not sure I really understand what
>> benefit we're getting out of this. If we lose a few WAL records for
>> an uncommitted transaction, who cares? That transaction is gone
>> anyway.
> Well, before the simple fix Simon applied after my initial complaint you
> didn't get wakeups *at all* in the synchronous_commit=off case.
>
> Now, with the additional changes, the walsender is woken exactly when data is
> available to send and not always when a commit happens. I played around with
> various scenarios and it always was a win.
Can you elaborate on that a bit? What scenarios did you play around
with, and what does "win" mean in this context?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | D'Arcy Cain | 2012-06-22 15:12:50 | Re: COMMUTATOR doesn't seem to work |
Previous Message | Tom Lane | 2012-06-22 14:56:10 | Re: [PATCH 04/16] Add embedded list interface (header only) |