| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Eliot Gable <egable+pgsql-general(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 23:11:46 |
| Message-ID: | 18356.1334704306@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Eliot Gable <egable+pgsql-general(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Ernst | 2012-04-18 00:03:37 | Re: Recreate primary key without dropping foreign keys? |
| Previous Message | Tom Lane | 2012-04-17 23:01:55 | Re: Feature Proposal: Constant Values in Columns or Foreign Keys |