Re: keeping WAL after dropping replication slots

Поиск
Список
Период
Сортировка
От Tom DalPozzo
Тема Re: keeping WAL after dropping replication slots
Дата
Msg-id CAK77FCSoaPfOPjyXCGBiR-dr7jbwOLehFAMs+aXfQH8Dn-woWw@mail.gmail.com
обсуждение исходный текст
Ответ на keeping WAL after dropping replication slots  (Tom DalPozzo <t.dalpozzo@gmail.com>)
Список pgsql-general
Дерево обсуждения
Hi,

2017-04-05 1:55 GMT+02:00 Adrian Klaver <adrian.klaver@aklaver.com>:
On 04/04/2017 07:45 AM, Tom DalPozzo wrote:

Postgres version?
9.6.1 

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?

I have 2 slaves configured with async replication but they were down  when I dropped the slots. 

So the 800 WALs number mean you have wal_keep_segments set to 800?
No,  wal_keep_segments is commented.
800 is the rough number of files I saw in xlog dir before dropping the slots.




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

Regards
Pupillo

В списке pgsql-general по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: AEXPR_OR, AEXPR_AND is not in postgres 9.6, how can Irewrite where it used in 9.3 ?
Следующее
От: Daniel Westermann
Дата:
Сообщение: Re: Query never completes with low work_mem (at least notwithin one hour)