Commit36113b4

authored and

committed

Make multixact error message more explicit

There are recent reports involving a very old error message that we haveno history of hitting -- perhaps a recently introduced bug. Improve theerror message in an attempt to improve our chances of investigating thebug.Per reports from Dimos Stamatakis and Bob Krier.Backpatch to 11.Discussion:https://postgr.es/m/CO2PR0801MB2310579F65529380A4E5EDC0E20A9@CO2PR0801MB2310.namprd08.prod.outlook.comDiscussion:https://postgr.es/m/17518-04e368df5ad7f2ee@postgresql.org

1 parent6f26c29 commit36113b4Copy full SHA for 36113b4

File tree

-1

lines changed

-1

lines changed

Lines changed: 2 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -799,7 +799,8 @@ MultiXactIdCreateFromMembers(int nmembers, MultiXactMember *members)`
`799`	`799`	`if (ISUPDATE_from_mxstatus(members[i].status))`
`800`	`800`	`{`
`801`	`801`	`if (has_update)`
`802`		`-elog(ERROR,"new multixact has more than one updating member");`
	`802`	`+elog(ERROR,"new multixact has more than one updating member: %s",`
	`803`	`+mxid_to_string(InvalidMultiXactId,nmembers,members));`
`803`	`804`	`has_update= true;`
`804`	`805`	`}`
`805`	`806`	`}`

Comments

(0)