From 2cf41cd30997f6a79fb962007a3cd11edcf9d013 Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Thu, 24 Nov 2022 10:45:10 +0100 Subject: [PATCH] Make multixact error message more explicit There are recent reports involving a very old error message that we have no history of hitting -- perhaps a recently introduced bug. Improve the error message in an attempt to improve our chances of investigating the bug. Per reports from Dimos Stamatakis and Bob Krier. Backpatch to 11. Discussion: https://postgr.es/m/CO2PR0801MB2310579F65529380A4E5EDC0E20A9@CO2PR0801MB2310.namprd08.prod.outlook.com Discussion: https://postgr.es/m/17518-04e368df5ad7f2ee@postgresql.org --- src/backend/access/transam/multixact.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/backend/access/transam/multixact.c b/src/backend/access/transam/multixact.c index 204aa95045..e1191a7564 100644 --- a/src/backend/access/transam/multixact.c +++ b/src/backend/access/transam/multixact.c @@ -799,7 +799,8 @@ MultiXactIdCreateFromMembers(int nmembers, MultiXactMember *members) if (ISUPDATE_from_mxstatus(members[i].status)) { if (has_update) - elog(ERROR, "new multixact has more than one updating member"); + elog(ERROR, "new multixact has more than one updating member: %s", + mxid_to_string(InvalidMultiXactId, nmembers, members)); has_update = true; } }