Re: pgsql: walreceiver uses a temporary replication slot by default - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pgsql: walreceiver uses a temporary replication slot by default
Date
Msg-id 20200319022617.GP214947@paquier.xyz
Whole thread Raw
In response to Re: pgsql: walreceiver uses a temporary replication slot by default  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-hackers
On Tue, Mar 17, 2020 at 11:39:11PM +0300, Sergei Kornilov wrote:
> We need this change to set is_temp_slot properly. PrimarySlotName
> GUC can usually be an empty string, so just "slotname != NULL" is
> not enough.

Yep, or a temporary slot would never be created even if there is no
slot defined, and the priority goes to primary_slot_name if set.

> I attached patch with this change.

Thanks, I have added a new open item for v13 to track this effort:
https://wiki.postgresql.org/wiki/PostgreSQL_13_Open_Items
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side
Next
From: Amit Langote
Date:
Subject: Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side