From: Daniel Gustafsson <dgustafsson@postgresql.org>
Date: Thu, 25 May 2023 10:43:16 +0000 (+0200)
Subject: doc: Fix example query for pg_walinspect
X-Git-Tag: REL_15_4~87
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=803a504342d7e41cd5a2ffea7fbcc20900fd1d0d;p=thirdparty%2Fpostgresql.git

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
---

diff --git a/doc/src/sgml/pgwalinspect.sgml b/doc/src/sgml/pgwalinspect.sgml
index 2954c3b3a7d..51592a5c338 100644
--- a/doc/src/sgml/pgwalinspect.sgml
+++ b/doc/src/sgml/pgwalinspect.sgml
@@ -154,8 +154,9 @@ block_ref        |
       function will raise an error. For example:
 <screen>
 postgres=# SELECT * FROM pg_get_wal_stats('0/1E847D00', '0/1E84F500')
-             WHERE count > 0 LIMIT 1 AND
-                   "resource_manager/record_type" = 'Transaction';
+           WHERE count > 0 AND
+                 "resource_manager/record_type" = 'Transaction'
+           LIMIT 1;
 -[ RECORD 1 ]----------------+-------------------
 resource_manager/record_type | Transaction
 count                        | 2