From 661bf96cd208238efb45c75e3af5ad400e5b0026 Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson Date: Thu, 25 May 2023 12:43:16 +0200 Subject: [PATCH] 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 Discussion: https://postgr.es/m/CACJufxHqXDr4NnmwmR6pEiVPAg54J0dgwMuYQzrH5BX6+NtF1g@mail.gmail.com Backpatch-through: 15 --- doc/src/sgml/pgwalinspect.sgml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/pgwalinspect.sgml b/doc/src/sgml/pgwalinspect.sgml index a1a4422fb4..762ad69817 100644 --- a/doc/src/sgml/pgwalinspect.sgml +++ b/doc/src/sgml/pgwalinspect.sgml @@ -250,8 +250,9 @@ block_fpi_data | For example: 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