Postgres Pro
Downloads
Home   >   mailing lists

Re: LOCK TABLE is not allowed in a non-volatile function - Mailing list pgsql-general

From Michael Nolan
Subject Re: LOCK TABLE is not allowed in a non-volatile function
Date
Msg-id CAOzAquK+s9TgLTT4ztafeWf=eUamUPFQXwrsvizDK_d6ukf6dQ@mail.gmail.com
Whole thread Raw
In response to LOCK TABLE is not allowed in a non-volatile function  (Eliot Gable <egable@gmail.com>)
Responses Re: LOCK TABLE is not allowed in a non-volatile function  (Eliot Gable <egable@gmail.com>)
List pgsql-general
Tree view


On Tue, Apr 17, 2012 at 5:20 PM, Eliot Gable <egable@gmail.com> wrote:



I cannot find a single non-volatile function in the call path; so I am baffled on where this error message is coming from. I would be thankful for any ideas anyone might have on where this error message might be coming from or how to locate where it is coming from.


According to the documentation, the current_timestamp family of functions is stable, could that be the cause?  Better yet, should it?
--
Mike Nolan

pgsql-general by date:

Previous
From: Eliot Gable
Date:
Subject: LOCK TABLE is not allowed in a non-volatile function
Next
From: Nils Gösche
Date:
Subject: Re: Feature Proposal: Constant Values in Columns or Foreign Keys