| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan de Visser <jan(at)de-visser(dot)net> |
| 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" |
| Date: | 2015-08-26 00:36:52 |
| Message-ID: | 26482.1440549412@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2015-08-26 00:55:48 | Re: Custom Scans and private data |
| Previous Message | Jan de Visser | 2015-08-26 00:15:17 | Re: Idea: closing the loop for "pg_ctl reload" |