Re: Fix for visibility check on 14.5 fails on tpcc with high concurrency

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Dimos Stamatakis <dimos(dot)stamatakis(at)servicenow(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, "simon(dot)riggs(at)enterprisedb(dot)com" <simon(dot)riggs(at)enterprisedb(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix for visibility check on 14.5 fails on tpcc with high concurrency
Date: 2022-11-25 19:58:19
Message-ID: 20221125195819.bvr6sa53txc7bax7@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022-Nov-25, Dimos Stamatakis wrote:

> So does this mean there is no race condition in this case and that
> this error is redundant?

No, it means I believe a bug exists but that I haven't spent enough time
on it to understand what it is.

Please do not top-post.
https://wiki.postgresql.org/wiki/Mailing_Lists#Email_etiquette_mechanics

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"La rebeldía es la virtud original del hombre" (Arthur Schopenhauer)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2022-11-25 20:20:02 Re: Report roles in pg_upgrade pg_ prefix check
Previous Message Tom Lane 2022-11-25 19:52:15 Rethinking the implementation of ts_headline()