ri_LockPKTuple misleading message - Mailing list pgsql-hackers

From jian he
Subject ri_LockPKTuple misleading message
Date
Msg-id CACJufxEG1JTCq4A1gnNAu-bGAq9Xn=Xkf7kC3TRWFz6iuUOuRA@mail.gmail.com
Whole thread
Responses Re: ri_LockPKTuple misleading message
List 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/



pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: Wrong results from inner-unique joins caused by collation mismatch
Next
From: Amit Langote
Date:
Subject: Re: ri_LockPKTuple misleading message