Commit661bf96

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 parent8f5e42d commit661bf96Copy full SHA for 661bf96

File tree

-2

lines changed

-2

lines changed

Lines changed: 3 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -250,8 +250,9 @@ block_fpi_data \|`
`250`	`250`	`For example:`
`251`	`251`	`<screen>`
`252`	`252`	`postgres=# SELECT * FROM pg_get_wal_stats('0/1E847D00', '0/1E84F500')`
`253`		`- WHERE count > 0 LIMIT 1 AND`
`254`		`- "resource_manager/record_type" = 'Transaction';`
	`253`	`+ WHERE count > 0 AND`
	`254`	`+ "resource_manager/record_type" = 'Transaction'`
	`255`	`+ LIMIT 1;`
`255`	`256`	`-[ RECORD 1 ]----------------+-------------------`
`256`	`257`	`resource_manager/record_type \| Transaction`
`257`	`258`	`count \| 2`

Comments

(0)