| From: | Matthias Apitz <guru(at)unixarea(dot)de> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: existing row not found by SELECT ... WHERE CTID = ? |
| Date: | 2022-05-25 12:01:12 |
| Message-ID: | 20220525120112.GA17@sh4-5.1blu.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
El día Mittwoch, Mai 25, 2022 a las 12:51:02 +0200, Laurenz Albe escribió:
> On Wed, 2022-05-25 at 11:21 +0200, Matthias Apitz wrote:
> > Is it possible that the PostgreSQL 13.1 server does something by its own to invalidate the rowid?
>
> No. PostgreSQL may remove a dead row, but a dead row is by definition
> no longer visible, so it wouldn't be found by a query.
We will solve the problem now with setting the session after connect to
SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL REPEATABLE READ;
(with an appropriate ESQL/C call). Any comments?
Thanks
matthias
--
Matthias Apitz, ✉ guru(at)unixarea(dot)de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Moench-Tegeder | 2022-05-25 12:27:50 | Re: existing row not found by SELECT ... WHERE CTID = ? |
| Previous Message | Laurenz Albe | 2022-05-25 10:51:02 | Re: existing row not found by SELECT ... WHERE CTID = ? |