Skip to content

Commit 661bf96

Browse files
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.com Backpatch-through: 15
1 parent 8f5e42d commit 661bf96

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

doc/src/sgml/pgwalinspect.sgml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -250,8 +250,9 @@ block_fpi_data |
250250
For example:
251251
<screen>
252252
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;
255256
-[ RECORD 1 ]----------------+-------------------
256257
resource_manager/record_type | Transaction
257258
count | 2

0 commit comments

Comments
 (0)