Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit1ab8fd2

Browse files
danielgustafssonpull[bot]
authored andcommitted
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 parent9c11452 commit1ab8fd2

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)

[8]ページ先頭

©2009-2025 Movatter.jp