Re: Can I just reload the slave to change primary_conninfo?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Sergei Kornilov <sk(at)zsrv(dot)org>
Cc: Chris Travers <chris(dot)travers(at)adjust(dot)com>, "luajit(dot)io(at)gmail(dot)com" <luajit(dot)io(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Can I just reload the slave to change primary_conninfo?
Date: 2018-09-11 03:14:09
Message-ID: 20180911031409.GC27115@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 10, 2018 at 06:12:52PM +0300, Sergei Kornilov wrote:
> There were already some discussions about move recovery.conf into GUC
> infrastructure first. I continue work on one most recent patch here:
> https://commitfest.postgresql.org/19/1711/ If this patch will be
> committed - i plan sent new patch to allow change primary_conninfo
> with SIGHUP.

Nice to hear that! Please make sure that in the first flavor of the
patch all the recovery parameters are switched to GUC_POSTMASTER so as
they map with the existing behavior. We should move a subset of those
parameters to SIGHUP after a careful lookup, and as a secondary step.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2018-09-11 03:49:43 Re: [HACKERS] Secondary index access optimizations
Previous Message Corey Huinker 2018-09-11 02:52:25 Re: CREATE ROUTINE MAPPING