[PATCH] Improve error message when trying to lock virtual tuple.

From: Sven Klemm <sven(at)timescale(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: [PATCH] Improve error message when trying to lock virtual tuple.
Date: 2024-06-17 15:55:37
Message-ID: CAMCrgp0TBCOWneX6oPpysR3gqp_njgNvBOd45wtpiwMjuoFeMQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

When currently trying to lock a virtual tuple the returned error
will be a misleading `could not read block 0`. This patch adds a
check for the tuple table slot being virtual to produce a clearer
error.

This can be triggered by extensions returning virtual tuples.
While this is of course an error in those extensions the resulting
error is very misleading.

--
Regards, Sven Klemm

Attachment Content-Type Size
0001-Improve-error-message-when-trying-to-lock-virtual-tu.patch text/x-patch 1.1 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2024-06-17 16:10:45 Re: using extended statistics to improve join estimates
Previous Message David E. Wheeler 2024-06-17 15:52:10 FYI: LLVM Runtime Crash