Re: keeping WAL after dropping replication slots - Mailing list pgsql-general

From Adrian Klaver
Subject Re: keeping WAL after dropping replication slots
Date
Msg-id 249b4b3b-d364-a8c6-187d-3778d1dca920@aklaver.com
Whole thread Raw
In response to keeping WAL after dropping replication slots  (Tom DalPozzo <t.dalpozzo@gmail.com>)
List pgsql-general
On 04/04/2017 07:45 AM, Tom DalPozzo wrote:

Postgres version?

> Hi,
> I had two replication slots on my primary. Slaves off and (around 800)
> WALs kept as expected.

Slaves off means?:

You replication set up from the master to the slaves(how many?).
Then you disconnected the slaves how?

So the 800 WALs number mean you have wal_keep_segments set to 800?



> I dropped those slots but over time, the system kept on adding new WALs
> without reusing them or deleting them.
> Only after shutdown and restart the system deleted those WAL files.
> Is that ok?
> regards
> Pupillo
>
>


--
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: "Armand Pirvu (home)"
Date:
Subject: Re: getting column names
Next
From: Bruno Wolff III
Date:
Subject: Is there a point to having both a normal gist index and an excludeindex?