aboutsummaryrefslogtreecommitdiff
path: root/src/backend
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2021-08-30 16:29:12 -0400
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2021-08-30 16:29:12 -0400
commit961dd7565726a507d4551f7ea54ad888fc6ee93a (patch)
treee80cd6fcdd576e2ce0861586bfa222403c8a823e /src/backend
parenta397109114c8569e21ed3c858a16143de28a1897 (diff)
downloadpostgresql-961dd7565726a507d4551f7ea54ad888fc6ee93a.tar.gz
postgresql-961dd7565726a507d4551f7ea54ad888fc6ee93a.zip
Report tuple address in data-corruption error message
Most data-corruption reports mention the location of the problem, but this one failed to. Add it. Backpatch all the way back. In 12 and older, also assign the ERRCODE_DATA_CORRUPTED error code as was done in commit fd6ec93bf890 for 13 and later. Discussion: https://postgr.es/m/202108191637.oqyzrdtnheir@alvherre.pgsql
Diffstat (limited to 'src/backend')
-rw-r--r--src/backend/access/heap/heapam_handler.c6
1 files changed, 5 insertions, 1 deletions
diff --git a/src/backend/access/heap/heapam_handler.c b/src/backend/access/heap/heapam_handler.c
index beb8f207088..9befe012a9e 100644
--- a/src/backend/access/heap/heapam_handler.c
+++ b/src/backend/access/heap/heapam_handler.c
@@ -424,7 +424,11 @@ tuple_lock_retry:
if (TransactionIdIsValid(SnapshotDirty.xmin))
ereport(ERROR,
(errcode(ERRCODE_DATA_CORRUPTED),
- errmsg_internal("t_xmin is uncommitted in tuple to be updated")));
+ errmsg_internal("t_xmin %u is uncommitted in tuple (%u,%u) to be updated in table \"%s\"",
+ SnapshotDirty.xmin,
+ ItemPointerGetBlockNumber(&tuple->t_self),
+ ItemPointerGetOffsetNumber(&tuple->t_self),
+ RelationGetRelationName(relation))));
/*
* If tuple is being updated by other transaction then we