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

Commit8f9b6d4

Browse files
committed
doc: Correct description of restart_lsn in pg_replication_slots
Previously the document explained that restart_lsn indicates the LSN ofoldest WAL won't be automatically removed during checkpoints. Butsince v13 this was no longer true thanks to max_slot_wal_keep_size.Back-patch to v13 where max_slot_wal_keep_size was added.Author: Fujii MasaoDiscussion:https://postgr.es/m/6497f1e9-3148-c5da-7e49-b2fddad9a42f@oss.nttdata.com
1 parentd1763ea commit8f9b6d4

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

‎doc/src/sgml/catalogs.sgml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11214,7 +11214,9 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
1121411214
<para>
1121511215
The address (<literal>LSN</literal>) of oldest WAL which still
1121611216
might be required by the consumer of this slot and thus won't be
11217-
automatically removed during checkpoints. <literal>NULL</literal>
11217+
automatically removed during checkpoints unless this LSN
11218+
gets behind more than <xref linkend="guc-max-slot-wal-keep-size"/>
11219+
from the current LSN. <literal>NULL</literal>
1121811220
if the <literal>LSN</literal> of this slot has never been reserved.
1121911221
</para></entry>
1122011222
</row>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp