| From: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Patroni, slots, and expiring WALs |
| Date: | 2023-03-28 15:53:42 |
| Message-ID: | 20230328155342.gmn33twufrwc7r65@hjp.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2023-03-28 17:27:27 +0200, Peter J. Holzer wrote:
> On 2023-03-28 17:08:38 +0200, Alexander Kukushkin wrote:
> > The second option - you can put all member names into permanent slots
> > configuration (using patronictl edit-config):
> > slots:
> > nodename1:
> > type: physical
> > nodename2:
> > type: physical
> > nodename3:
> > type: physical
> >
> > This way slots representing these members will not be removed.
>
> That seems to work (at least the slot didn't disappear within a few
> minutes). I'll do some more testing.
Works nicely. Thanks!
hp
--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp(at)hjp(dot)at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2023-03-28 16:05:54 | Re: Cluster table based on grand parent? |
| Previous Message | Peter J. Holzer | 2023-03-28 15:27:27 | Re: Patroni, slots, and expiring WALs |