|From:||Jan de Visser <jan(at)de-visser(dot)net>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Cc:||Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Idea: closing the loop for "pg_ctl reload"|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On August 25, 2015 08:36:52 PM Tom Lane wrote:
> Jan de Visser <jan(at)de-visser(dot)net> writes:
> > On August 25, 2015 09:31:35 PM Michael Paquier wrote:
> >> This patch had feedback, but there has been no update in the last
> >> month, so I am now marking it as returned with feedback.
> > It was suggested that this mechanism became superfluous with the inclusion
> > of the view postgresql.conf (pg_settings?) in 9.5. I left it to Tom
> > (being the one that suggested the feature) to indicate if he still thinks
> > it's useful.
> I think there's still a fair argument for "pg_ctl reload" being able to
> return a simple yes-or-no result. We had talked about trying to shoehorn
> textual error messages into the protocol, and I'm now feeling that that
> complication isn't needed, but a bare-bones feature would still be worth
> the trouble IMO.
OK, I'll have a look at the review comments and submit something updated soon.
|Next Message||Amit Kapila||2015-08-26 02:45:38||Re: Make HeapTupleSatisfiesMVCC more concurrent|
|Previous Message||Tom Lane||2015-08-26 01:57:51||Re: [PATCH] Reload SSL certificates on SIGHUP|