Commit803a504

committed

doc: Fix example query for pg_walinspect

The LIMIT clause had ended up in the wrong place in the query.Backpatch to v15 where pg_walinspect was introduced.Reported-by: Jian He <jian.universality@gmail.com>Discussion:https://postgr.es/m/CACJufxHqXDr4NnmwmR6pEiVPAg54J0dgwMuYQzrH5BX6+NtF1g@mail.gmail.comBackpatch-through: 15

1 parent34f5119 commit803a504Copy full SHA for 803a504

File tree

-2

lines changed

-2

lines changed

Lines changed: 3 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -154,8 +154,9 @@ block_ref \|`
`154`	`154`	`function will raise an error. For example:`
`155`	`155`	`<screen>`
`156`	`156`	`postgres=# SELECT * FROM pg_get_wal_stats('0/1E847D00', '0/1E84F500')`
`157`		`- WHERE count > 0 LIMIT 1 AND`
`158`		`- "resource_manager/record_type" = 'Transaction';`
	`157`	`+ WHERE count > 0 AND`
	`158`	`+ "resource_manager/record_type" = 'Transaction'`
	`159`	`+ LIMIT 1;`
`159`	`160`	`-[ RECORD 1 ]----------------+-------------------`
`160`	`161`	`resource_manager/record_type \| Transaction`
`161`	`162`	`count \| 2`

Comments

(0)