postgres.git / summary / log / commit / refs

commit    b20e381422089f66d2cfa7a6286c8053006d3afb
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Thu Nov 24 09:45:10 2022 +0000
First released in: 16.0, 11.19, 12.14, 13.10, 14.7, 15.2

    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 ad9e7ff8f05..672818f75ce 100644
--- a/src/backend/access/transam/multixact.c
+++ b/src/backend/access/transam/multixact.c
@@ -779,7 +779,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;
 			}
 		}


[parent: 2f92b8ad3121]