Re: SELECT FOR UPDATE regression in 9.5

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Jaan-Magnus Tammepuu <magnus(at)voicecom(dot)ee>
Subject: Re: SELECT FOR UPDATE regression in 9.5
Date: 2016-09-06 17:03:42
Message-ID: 3b06698c-b8f7-2e62-fffd-f4137b740292@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2016-09-06 6:02 PM, Marti Raudsepp wrote:
> This issue is also reproducible on the current master branch. In an
> assertions-enabled build, it traps an assertion in HeapTupleHeaderGetCmax
> called by heap_lock_tuple. The following test case demonstrates the issue...

I think you found a reproducible test case for my bug in
48d3eade-98d3-8b9a-477e-1a8dc32a724d(at)joh(dot)to(dot) Thanks.

.m

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-09-06 17:08:51 Re: Re: [COMMITTERS] pgsql: Make initdb's suggested "pg_ctl start" command line more reliabl
Previous Message Tom Lane 2016-09-06 17:00:45 Re: (Comment)Bug in CteScanNext