Re: BUG #14972: row duplicate on first SELECT from CTE (by JOIN/FOR UPDATE) from which UPDATE performed recently

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Evgeniy Kozlov <dsuchka(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14972: row duplicate on first SELECT from CTE (by JOIN/FOR UPDATE) from which UPDATE performed recently
Date: 2017-12-14 12:52:47
Message-ID: CAL9smLAg6HLeCdo6U9fgMJRCdma=XeK2N0s9wsAtmqCCOpLqiA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I'm just guessing here, but since concurrency, CTEs and scalar subqueries
are involved, I wonder if the underlying cause is the same as the one for
BUG #14870 ? (That one's still undiagnosed, but it has a simpler test
case.)

.m

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jarosław Stokłosa 2017-12-14 12:56:11 Re: BUG #14974: count doesn't accept text columns
Previous Message Marko Tiikkaja 2017-12-14 12:47:34 Re: BUG #14974: count doesn't accept text columns