Re: LOCK TABLE is not allowed in a non-volatile function

From: Michael Nolan <htfoot(at)gmail(dot)com>
To: Eliot Gable <egable(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: LOCK TABLE is not allowed in a non-volatile function
Date: 2012-04-17 21:55:10
Message-ID: CAOzAquK+s9TgLTT4ztafeWf=eUamUPFQXwrsvizDK_d6ukf6dQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Apr 17, 2012 at 5:20 PM, Eliot Gable <egable(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Eliot Gable 2012-04-17 22:02:42 Re: LOCK TABLE is not allowed in a non-volatile function
Previous Message Eliot Gable 2012-04-17 21:20:55 LOCK TABLE is not allowed in a non-volatile function