| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | Chris Travers <chris(dot)travers(at)adjust(dot)com>, "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz> |
| Cc: | "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-10 15:12:52 |
| Message-ID: | 13073111536592372@sas1-9414422abf7c.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello
> Is there any reason this cannot be changed via a signal? Is it a general lack of infrastructure or is it there significant problem we want to ensure never happens?
Just make possible reload recovery.conf is not what the pgsql-hackers community want. My patch with exactly this feature was rejected with this reason.
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.
regards, Sergei
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mithun Cy | 2018-09-10 16:08:15 | Re: Pluggable Storage - Andres's take |
| Previous Message | Chris Travers | 2018-09-10 14:53:24 | Re: Can I just reload the slave to change primary_conninfo? |