Re: Question on STABLE functions limitations

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marc Mamin" <M(dot)Mamin(at)intershop(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Question on STABLE functions limitations
Date: 2010-10-18 14:18:28
Message-ID: 19012.1287411508@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Marc Mamin" <M(dot)Mamin(at)intershop(dot)de> writes:
> I wonder if there are some special cases where STABLE functions should
> be avoided.

> I think for example of functions using set_config or querying the
> advisory locks.

set_config has side-effects and hence should not be done in non-volatile
functions.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Robert Haas 2010-10-18 14:27:37 Re: [GENERAL] column-level update privs + lock table
Previous Message Josh Kupershmidt 2010-10-18 14:12:19 Re: How to change pg_trigger query so that it works in 9.0 without pg_trigger.tgisconstraint does not exist error