From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Spencer Riddering" <spencer(at)riddering(dot)net> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1550: LOCK TABLE in plpgsql function doesn't work. |
Date: | 2005-03-18 06:17:07 |
Message-ID: | 3491.1111126627@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Spencer Riddering" <spencer(at)riddering(dot)net> writes:
> When a LOCK TABLE statement is included in a plpgsql function it does not
> actually lock the table.
Sure it does. If it doesn't, your test case surely will not prove it;
you cannot prove the existence or lack of existence of a lock in a test
case with only one connection...
I suspect your complaint really has to do with the fact that the
transaction snapshot is established before the function is entered,
and thus before the lock is taken. Pre-8.0, we did not advance the
snapshot within functions, and so the commands within the function
would all see a snapshot that predated the obtaining of the lock.
Short answer: try 8.0.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-03-18 06:37:43 | Re: BUG #1550: LOCK TABLE in plpgsql function doesn't work. |
Previous Message | Michael Fuhr | 2005-03-18 06:02:50 | Re: BUG #1551: You need an import/export feature |