Should we warn users about SETs which have no effect? - Mailing list pgsql-hackers

From Josh Berkus
Subject Should we warn users about SETs which have no effect?
Date
Msg-id 4AE72178.1020506@agliodbs.com
Whole thread Raw
Responses Re: Should we warn users about SETs which have no effect?
List pgsql-hackers
Hackers,

There are some GUCs you can set in a context which will accept them, yet
they have no effect when you do.  For example, I can call SET
statement_timeout inside a function, and it has no effect whatsoever.

I'm wondering if we should be throwing a warning in these cases.  And
how many such cases there are.  Thoughts?

--Josh Berkus


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Scaling up deferred unique checks and the after trigger queue
Next
From: Josh Berkus
Date:
Subject: Re: Proposal: String key space for advisory locks