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

From Josh Berkus
Subject Re: Should we warn users about SETs which have no effect?
Date
Msg-id 4AE7277F.3040708@agliodbs.com
Whole thread Raw
In response to Should we warn users about SETs which have no effect?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 10/27/09 9:36 AM, Josh Berkus wrote:
> 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?

Hmmmm, clarification: this applies to SET LOCAL, specifically.

---Josh


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Delete cascade with three levels bug ?
Next
From: Robert Haas
Date:
Subject: Re: FOR UPDATE versus WITH --- change 8.4 too?