From: | Fabrice Chapuis <fabrice636861(at)gmail(dot)com> |
---|---|
To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Problem managing slots in Patroni |
Date: | 2024-02-06 08:03:02 |
Message-ID: | CAA5-nLCaq_sXO8FVw4bHVAfyCzY7genmHqXqTgBrjKbBsYWZNw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I use patroni version 3.2.1. There is a point that I do not understand in
the slots management with Patroni.
Patroni creates a slot automatically on primary node when there is a
standby attached, although this slot does not belong to the patroni
configuration.
How to prevent the automatic creation of this slot?
Thanks for helping
Here is Patroni configuration:
slots:
barman_x:
type: physical
barman_y:
type: physical
logic_slot:
database: test
plugin: pgoutput
postgresql:
use_pg_rewind: true
use_slots: true
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2024-02-06 09:32:23 | Re: Unused indexes |
Previous Message | Shaheed Haque | 2024-02-06 07:31:40 | Re: Improving pg_dump performance when handling large numbers of LOBs |