Re: BUG #9557: Row not visible after receiving notification

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #9557: Row not visible after receiving notification
Date: 2014-03-13 13:55:44
Message-ID: 5321B8E0.9040601@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 3/13/14 2:45 PM, Heikki Linnakangas wrote:
> On 03/13/2014 03:26 PM, Marko Tiikkaja wrote:
>> On 3/13/14 1:55 PM, I wrote:
>>> This would explain it, as I don't see the notification code checking
>>> whether the transaction is still in PGPROC, just calling
>>> TransactionIdDidCommit().
>>
>> And as predicted, adding a call to TransactionIdIsInProgress() in
>> asyncQueueProcessPageEntries makes the problem go away.
>
> Good catch! Want to write that into a patch?

I can do it if it helps, but I figured that it's a one-line change,
perhaps four with a nice comment..

Regards,
Marko Tiikkaja

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-03-13 13:56:35 Re: BUG #9552: IndexOnlyScan startup_cost>0, why not equal 0?it's a bug?
Previous Message Alvaro Herrera 2014-03-13 13:47:39 Re: BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns