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

From Sergei Kornilov
Subject Re: pgsql: walreceiver uses a temporary replication slot by default
Date
Msg-id 15987771581947824@iva1-398527a32f9a.qloud-c.yandex.net
Whole thread Raw
In response to Re: pgsql: walreceiver uses a temporary replication slot by default  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pgsql: walreceiver uses a temporary replication slot by default
List pgsql-hackers
Hello

> Thanks for posting this patch, Sergei. Here is a review to make
> things move on.

Thank you, here is updated patch

> The set of comments you are removing from walreceiver.c to decide if a
> temporary slot needs to be created or not should be moved to
> walreceiverfuncs.c as you move the logic from the WAL receiver startup
> phase to the moment the WAL receiver spawn is requested.

I changed this comments because they describes behavior during change value of wal_receiver_create_temp_slot.
But yes, I need to add some comments to RequestXLogStreaming.

> It would be more consistent with primary_conn_info and
> primary_slot_name if wal_receiver_create_temp_slot is passed down as
> an argument of RequestXLogStreaming().

Yep, I thought about that. Changed.

> As per the discussion done on this thread, let's also switch the
> parameter default to be disabled.

Done (my vote is also for disabling this option by default).

regards, Sergei
Attachment

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Wait event that should be reported while waiting for WALarchiving to finish
Next
From: Tom Lane
Date:
Subject: Re: Fix compiler warnings on 64-bit Windows