Re: [patch] [doc] Clarify that signal functions have no feedback - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [patch] [doc] Clarify that signal functions have no feedback
Date
Msg-id 2f765a90-5ae4-e533-43e8-407b587895b2@2ndquadrant.com
Whole thread Raw
In response to [patch] [doc] Clarify that signal functions have no feedback  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: [patch] [doc] Clarify that signal functions have no feedback
List 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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Make procedure OUT parameters work with JDBC
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Runtime control of CLOBBER_CACHE_ALWAYS