| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [patch] [doc] Clarify that signal functions have no feedback |
| Date: | 2020-10-27 08:19:57 |
| Message-ID: | 2f765a90-5ae4-e533-43e8-407b587895b2@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-10-13 00:43, David G. Johnston wrote:
> Over in Bug# 16652 [1] Christoph failed to recognize the fact that
> signal sending functions are inherently one-way just as signals are. It
> seems worth heading off this situation in the future by making it clear
> how signals behave and, in the specific case of pg_reload_conf, that the
> important feedback one would hope to get out of a success/failure
> response from the function call must instead be found in other locations.
I agree that the documentation could be improved here. But I don't see
how the added advice actually helps in practice. How can you detect
reload errors by inspecting pg_settings etc.?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-10-27 08:34:48 | Re: [PATCH] Runtime control of CLOBBER_CACHE_ALWAYS |
| Previous Message | Peter Eisentraut | 2020-10-27 08:12:20 | Re: Make procedure OUT parameters work with JDBC |