Re: existing row not found by SELECT ... WHERE CTID = ?

From: Matthias Apitz <guru(at)unixarea(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: existing row not found by SELECT ... WHERE CTID = ?
Date: 2022-05-27 16:36:36
Message-ID: YpD+FKxH1CdP7sGZ@pureos
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

El día jueves, mayo 26, 2022 a las 12:02:35 -0400, Tom Lane escribió:

> I wonder though if the
> OP should be considering using SELECT FOR UPDATE in his cursor,
> so that it'd automatically chain up to the newest row version.

I diged into this but the CURSOR are all declared WITH HOLD and this
conflicts with FOR UPDATE. And this is not easy to change in our generic
generated DB-layer for all the ~400 tables.

matthias

--
Matthias Apitz, ✉ guru(at)unixarea(dot)de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2022-05-27 16:40:58 Re: Determine if range list contains specified integer
Previous Message Masahiko Sawada 2022-05-27 16:15:18 Re: Support logical replication of DDLs