From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: race condition in sync rep |
Date: | 2011-03-26 16:16:02 |
Message-ID: | AANLkTimoTHQyO4ZpE50Lo+9QJ5Gs6SWmX=o9nfB3oWty@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Mar 26, 2011 at 4:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> I've added code for you.
>
>> Your skepticism seems out of place. I actually hit this problem in testing. We could debate how realistic my test setup was, but why? It is not our policy - and bad practice in general - to ship code with race conditions. The code you added is not "for me"; it's "to fix a race condition".
>
> In particular, in view of today's fix, shouldn't this commit be reverted?
>
> http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6e8e7cc580665ddd43c8ca2acc6d60f345570a57
>
> I thought at the time that that was nothing more than documenting a
> known bug, and now it is documenting a dead bug.
No, that doc change is still accurate.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-03-26 16:21:07 | Re: race condition in sync rep |
Previous Message | Simon Riggs | 2011-03-26 16:12:24 | Re: Lock problem with autovacuum truncating heap |