On Wed, Dec 20, 2017 at 10:00 PM, Feike Steenbergen
<feikesteenber...@gmail.com> wrote:
> As far as I know the issue only occurs for stale replication slots for
> logical decoding but not for physical replication, is that correct?
Yeah, I recall something similar.
@@ -255,7 +255,9 @@ $ pg_recvlogical -d postgres --slot test --drop-slot
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 <command>VACUUM</command> 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 <xref linkend="vacuum-for-wraparound"/>).
+ So if a slot is no longer required it should be dropped.
</para>
Don't you want to put that in its own <caution> block? That's rather
important not to miss for administrators.
--
Michael
