Re: base backup client as auxiliary backend process

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>
Cc: Sergei Kornilov <sk(at)zsrv(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: base backup client as auxiliary backend process
Date: 2020-01-14 13:58:23
Message-ID: 7925a361-d48c-db03-30b4-fcd331ef7f02@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-01-14 07:32, Masahiko Sawada wrote:
> - <entry>Replication slot name used by this WAL receiver</entry>
> + <entry>
> + Replication slot name used by this WAL receiver. This is only set if a
> + permanent replication slot is set using <xref
> + linkend="guc-primary-slot-name"/>. Otherwise, the WAL receiver may use
> + a temporary replication slot (determined by <xref
> + linkend="guc-wal-receiver-create-temp-slot"/>), but these are not shown
> + here.
> + </entry>
>
> Now that the slot name is shown even if it's a temp slot the above
> documentation changes needs to be changed. Other changes look good to
> me.

committed, thanks

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message 曾文旌 (义从) 2020-01-14 14:15:11 Re: [Proposal] Global temporary tables
Previous Message Peter Eisentraut 2020-01-14 13:57:34 pgsql: walreceiver uses a temporary replication slot by default