Re: Allowing pg_recvlogical to create temporary replication slots

From: "Dickson S(dot) Guedes" <guedes(at)guedesoft(dot)net>
To: Torsten Förtsch <tfoertsch123(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Allowing pg_recvlogical to create temporary replication slots
Date: 2024-11-12 14:30:43
Message-ID: CALwLAkRss6q0CcWx29o4pdqNB0BpVbf8kit+xFUXWeUD2709XQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em ter., 12 de nov. de 2024 às 07:54, Torsten Förtsch
<tfoertsch123(at)gmail(dot)com> escreveu:
> Hi Dickson,
>
> [ ... ]
>
> If the slot existed before, the existing slot will be used, no error is generated. In that case the slot will keep existing when the connection is dropped.
>
> The following situation can happen:
> - the slot does not exist and is created as a temporary slot
> - the connection drops and pg_recvlogical tries to reconnect after a few seconds
> - in that period a permanent slot by the same name is created but no reader is connected to it
> - pg_recvlogical reconnects and finds the existing slot
>
> In this case, the now existing slot is simply used. It will remain when the connection is dropped.
>
> Thanks for reviewing.

Thank you for your clarification.

Are you planning to add changes in docs? Would be important to have
this clarification in there also, IMHO.

Regards.
--
Dickson S. Guedes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2024-11-12 14:37:02 Re: [PATCH] Refactor SLRU to always use long file names
Previous Message Aleksander Alekseev 2024-11-12 14:15:52 Re: [PATCH] Refactor SLRU to always use long file names