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: Should we warn users about SETs which have no effect?
Date: 2009-10-27 16:36:08
Message-ID: 4AE72178.1020506@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2009-10-27 16:43:20 Re: Proposal: String key space for advisory locks
Previous Message Jeff Davis 2009-10-27 16:13:26 Re: Scaling up deferred unique checks and the after trigger queue