From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Torsten Förtsch <tfoertsch123(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Allowing pg_recvlogical to create temporary replication slots |
Date: | 2024-11-04 06:13:48 |
Message-ID: | ZyhmHA9BH07LfWem@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 01, 2024 at 01:42:55PM +0100, Torsten Förtsch wrote:
> I was in the process of experimenting with this idea and found that
> pg_recvlogical can:
> - only create the slot or
> - create the slot and immediately use it
> - try to create the slot and if the slot is already there use it
>
> So, why not also allow it to create a temporary slot?
I have no objections. I don't really have an argument regarding the
use cases for specific applications, but I can see myself use this
option for development purposes: I have some experience using
pg_recvlogical for debugging purposes with logical decoding plugins in
the past, requiring always prior replication slot creation.
I can also imagine someone willing to use it on a live server and make
sure that there is no replication slot left behind once the tool has
disconnected on the receiver side.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | jian he | 2024-11-04 07:16:35 | Re: general purpose array_sort |
Previous Message | Michael Paquier | 2024-11-04 06:04:09 | Re: pgsql: Implement pg_wal_replay_wait() stored procedure |