Re: Should we warn users about SETs which have no effect?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Should we warn users about SETs which have no effect?
Date: 2009-10-27 17:01:51
Message-ID: 4AE7277F.3040708@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-10-27 17:02:53 Re: FOR UPDATE versus WITH --- change 8.4 too?
Previous Message Robert Haas 2009-10-27 17:00:49 Re: Delete cascade with three levels bug ?