Search Postgresql Archives

keeping WAL after dropping replication slots

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: keeping WAL after dropping replication slots
From: Tom DalPozzo <t.dalpozzo@xxxxxxxxx>
Date: Tue, 4 Apr 2017 16:45:54 +0200

Hi,

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

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: keeping WAL after dropping replication slots
  - From: Adrian Klaver

Prev by Date: Re: Query never completes with low work_mem (at least not within one hour)
Next by Date: Re: audit function and old.column
Previous by thread: Query never completes with low work_mem (at least not within one hour)
Next by thread: Re: keeping WAL after dropping replication slots
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux