Re: base backup client as auxiliary backend process - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: base backup client as auxiliary backend process
Date
Msg-id 4c79f835-b443-7b02-9097-aa1a40f46be9@2ndquadrant.com
Whole thread Raw
In response to Re: base backup client as auxiliary backend process  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Responses Re: base backup client as auxiliary backend process
Re: base backup client as auxiliary backend process
List pgsql-hackers
On 2020-01-10 04:32, Masahiko Sawada wrote:
> I agreed that these patches are useful on its own and 0001 patch and

committed 0001

> 0002 patch look good to me. For 0003 patch,
> 
> +      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.
> 
> I think it's better to show the temporary slot name on
> pg_stat_wal_receiver view. Otherwise user would have no idea about
> what wal receiver is using the temporary slot.

Makes sense.  It makes the code a bit more fiddly, but it seems worth 
it.  New patches attached.

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

Attachment

pgsql-hackers by date:

Previous
From: Kohei KaiGai
Date:
Subject: Re: How to retain lesser paths at add_path()?
Next
From: Artur Zakirov
Date:
Subject: Re: Add pg_file_sync() to adminpack