Vladimir Sitnikov <sitnikov.vladi...@gmail.com> writes:
> Here's my question: why change in search_path does NOT generate
> ParameterStatus message from the backend?
The protocol specification includes a list of the small number of GUCs
for which ParameterStatus messages are generated, and that is not one
of them.
This has been discussed before, I believe, and the conclusion was that
if you think you need this, you're doing it wrong. More robust solutions
involve having individual functions use SET clauses to locally force
search_path to be what they want. If we had search_path marked as
GUC_REPORT, that would both lead to a storm of useless client messages
when such techniques were in use, and encourage people to use methods
that won't really work reliably.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
