Commit9d0b5e8

Amit Kapila

authored and

committed

Fix the display of lock information for specktoken.

A transaction id is now displayed in the transactionid field andspeculative insertion token is displayed in the objid field.Author: Sawada MasahikoReviewed-by: Amit KapilaDiscussion:https://postgr.es/m/CAD21AoCEKxZztULP1CDm45aSNNR1QO-Bh1q6LMTspQ78PBuJrw@mail.gmail.com

1 parent11494db commit9d0b5e8Copy full SHA for 9d0b5e8

File tree

+18

-0

lines changed

+18

-0

lines changed

Lines changed: 6 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -1579,6 +1579,12 @@`
`1579`	`1579`	`permanent transaction ID of the current holder of that row lock.`
`1580`	`1580`	`</para>`
`1581`	`1581`
	`1582`	`+ <para>`
	`1583`	`+ A specualtive insertion lock consists of a transaction ID and a speculative`
	`1584`	`+ insertion token. The speculative insertion token is displayed in the`
	`1585`	`+ <structfield>objid</structfield> column.`
	`1586`	`+ </para>`
	`1587`	`+`
`1582`	`1588`	`<para>`
`1583`	`1589`	`Advisory locks can be acquired on keys consisting of either a single`
`1584`	`1590`	`<type>bigint</type> value or two integer values.`

Lines changed: 12 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -313,6 +313,18 @@ pg_lock_status(PG_FUNCTION_ARGS)`
`313`	`313`	`nulls[8]= true;`
`314`	`314`	`nulls[9]= true;`
`315`	`315`	`break;`
	`316`	`+caseLOCKTAG_SPECULATIVE_TOKEN:`
	`317`	`+values[6]=`
	`318`	`+TransactionIdGetDatum(instance->locktag.locktag_field1);`
	`319`	`+values[8]=ObjectIdGetDatum(instance->locktag.locktag_field2);`
	`320`	`+nulls[1]= true;`
	`321`	`+nulls[2]= true;`
	`322`	`+nulls[3]= true;`
	`323`	`+nulls[4]= true;`
	`324`	`+nulls[5]= true;`
	`325`	`+nulls[7]= true;`
	`326`	`+nulls[9]= true;`
	`327`	`+break;`
`316`	`328`	`caseLOCKTAG_APPLY_TRANSACTION:`
`317`	`329`	`values[1]=ObjectIdGetDatum(instance->locktag.locktag_field1);`
`318`	`330`	`values[8]=ObjectIdGetDatum(instance->locktag.locktag_field2);`

Comments

(0)