Horton
Menu

ri_LockPKTuple misleading message

jian he <jian.universality@gmail.com>

View thread
From: jian he <jian.universality@gmail.com>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Amit Langote <amitlangote09@gmail.com>
Date: 2026-04-25T10:52:52Z
Lists: pgsql-hackers 
Hi.

https://git.postgresql.org/cgit/postgresql.git/commit/?id=2da86c1ef9b5446e0e22c0b6a5846293e58d98e3
+ case TM_Deleted:
+ if (IsolationUsesXactSnapshot())
+ ereport(ERROR,
+ (errcode(ERRCODE_T_R_SERIALIZATION_FAILURE),
+ errmsg("could not serialize access due to concurrent update")));

errmsg should be
errmsg("could not serialize access due to concurrent delete")));
?

ExecLockRows also has the same situation.



--
jian
https://www.enterprisedb.com/

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Use "concurrent delete" in serialization error for TM_Deleted cases

  2. Add fast path for foreign key constraint checks