Re: Continue work on changes to recovery.conf API

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, David Steele <david(at)pgmasters(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, Sergei Kornilov <sk(at)zsrv(dot)org>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Continue work on changes to recovery.conf API
Date: 2018-11-27 17:11:38
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


* Andres Freund (andres(at)anarazel(dot)de) wrote:
> On 2018-11-27 15:36:59 +0100, Peter Eisentraut wrote:
> > That might be a useful facility, but it wouldn't really address the
> > pg_basebackup -R issue, because that creates settings that you don't
> > want going away in this manner.
> Why is that / which are those? It's not like it worked like that <
> 2dedf4d9.

primary_conninfo and restore_command are the main ones, and the idea is
that you'd like those to be specified even when you aren't in recovery,
so that you can have a symmetric config for when a given system does
become a replica.



In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-11-27 17:30:12 Re: Python versions (was Re: RHEL 8.0 build)
Previous Message Tomas Vondra 2018-11-27 16:51:43 Re: Sequential UUID Generation