mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Make multixact error message more explicit

Browse Source 
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
This commit is contained in:
Alvaro Herrera 2022-11-24 10:45:10 +01:00
parent f4b777e77d
commit 5a185246f9
No known key found for this signature in database
GPG Key ID: 1C20ACB9D5C564AE
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/backend/access/transam/multixact.c
View File

@ -781,7 +781,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;
}
}