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

From Eliot Gable
Subject Re: LOCK TABLE is not allowed in a non-volatile function
Date
Msg-id CAD-6L_XQ-yO5B6sifxBLzBVgQ0WWKYp+DB2_1bnm8vaYOOBCSw@mail.gmail.com
Whole thread Raw
In response to Re: LOCK TABLE is not allowed in a non-volatile function  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: LOCK TABLE is not allowed in a non-volatile function  (Eliot Gable <egable+pgsql-general@gmail.com>)
List pgsql-general
On Tue, Apr 17, 2012 at 7:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Eliot Gable <egable+pgsql-general@gmail.com> writes:
> When the trigger fires, I get this in my postgres.log file:
> 2012-04-17 16:57:15 EDT|test_db|169.254.5.138(56783)|****|[unknown]|30474
>  WARNING:  Failed to materialize the live_user_activity table; code 0A000:
> LOCK TABLE is not allowed in a non-volatile function

> 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'm confused too, but I'm not going to guess at details of an incomplete
example; the problem could well be related to code you didn't show us.
Please provide a self-contained script that triggers this message.
Also, what PG version are we talking about?

                       regards, tom lane

Thanks, Tom. I will try to get an entire example put together which I can post which will reproduce it. For your reference, the code I cut out was just inserts, updates, selects, and if/then/else statements. There were no other stored procedure calls or function calls present in any of the code I cut out.


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Compile docs on ArchLinux
Next
From: Vincent Veyron
Date:
Subject: Re: Feature Proposal: Constant Values in Columns or Foreign Keys