8000 Make multixact error message more explicit · postgres/postgres@b20e381 · GitHub
[go: up one dir, main page]

Skip to content

Commit b20e381

Browse files
committed
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
1 parent 2f92b8a commit b20e381

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

src/backend/access/transam/multixact.c

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -779,7 +779,8 @@ MultiXactIdCreateFromMembers(int nmembers, MultiXactMember *members)
779779
if (ISUPDATE_from_mxstatus(members[i].status))
780780
{
781781
if (has_update)
782-
elog(ERROR, "new multixact has more than one updating member");
782+
elog(ERROR, "new multixact has more than one updating member: %s",
783+
mxid_to_string(InvalidMultiXactId, nmembers, members));
783784
has_update = true;
784785
}
785786
}

0 commit comments

Comments
 (0)
0