Skip site navigation (1) Skip section navigation (2)

Re: BUG #1550: LOCK TABLE in plpgsql function doesn't work.

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 (view raw or flat)
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

In response to

pgsql-bugs by date

Next:From: Michael FuhrDate: 2005-03-18 06:37:43
Subject: Re: BUG #1550: LOCK TABLE in plpgsql function doesn't work.
Previous:From: Michael FuhrDate: 2005-03-18 06:02:50
Subject: Re: BUG #1551: You need an import/export feature

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group