Re: Idea: closing the loop for "pg_ctl reload" - Mailing list pgsql-hackers

From Jan de Visser
Subject Re: Idea: closing the loop for "pg_ctl reload"
Date
Msg-id 1659246.P8BIyfxrNh@bison
Whole thread Raw
In response to Re: Idea: closing the loop for "pg_ctl reload"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On August 25, 2015 08:36:52 PM Tom Lane wrote:
> Jan de Visser <jan@de-visser.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.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Reload SSL certificates on SIGHUP
Next
From: Amit Kapila
Date:
Subject: Re: Make HeapTupleSatisfiesMVCC more concurrent