From 2958a672b1fed35403b23c2b453aede9f7ef4b39 Mon Sep 17 00:00:00 2001 From: Simon Riggs Date: Fri, 29 Dec 2017 14:01:25 +0000 Subject: Extend near-wraparound hints to include replication slots Author: Feike Steenbergen Reviewed-by: Michael Paquier --- doc/src/sgml/logicaldecoding.sgml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml index 6bab1b9b322..fa101937e54 100644 --- a/doc/src/sgml/logicaldecoding.sgml +++ b/doc/src/sgml/logicaldecoding.sgml @@ -248,16 +248,18 @@ $ pg_recvlogical -d postgres --slot test --drop-slot may consume changes from a slot at any given time. - + Replication slots persist across crashes and know nothing about the state of their consumer(s). They will prevent removal of required resources even when there is no connection using them. This consumes storage because neither required WAL nor required rows from the system catalogs can be removed by VACUUM as long as they are required by a replication - slot. So if a slot is no longer required it should be dropped. + slot. In extreme cases this could cause the database to shut down to prevent + transaction ID wraparound (see ). + So if a slot is no longer required it should be dropped. - + -- cgit v1.2.3