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

RE: disallow LOCK on a view - the Tom Lane remix

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Alfred Perlstein" <bright(at)wintelcom(dot)net>, "Mark Hollomon" <mhh(at)mindspring(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: disallow LOCK on a view - the Tom Lane remix
Date: 2000-08-29 23:34:48
Message-ID: 000001c01211$b8c90660$2801007e@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
> -----Original Message-----
> From: Alfred Perlstein
> 
> * Mark Hollomon <mhh(at)mindspring(dot)com> [000829 11:26] wrote:
> > Here is a patch against CVS (without my earlier patch)
> > to disallow
> > 
> > LOCK x
> > 
> > if x is a view.
> > 
> > It does not use the SPI interface.
> 
> Waitasec, why??  This can be very useful if you want to atomically lock
> something that sits "in front" of several other tables that you need to
> do something atomically with.
> 
> Does it cause corruption if allowed?
>

If I remember correctly,the problem is "LOCK VIEW" acquires a
lock for the target view itself but doesn't acquire the lock for the
base tables of the view.

Regards.

Hiroshi Inoue

In response to

pgsql-hackers by date

Next:From: Alfred PerlsteinDate: 2000-08-30 00:23:02
Subject: Re: disallow LOCK on a view - the Tom Lane remix
Previous:From: Alfred PerlsteinDate: 2000-08-29 23:14:00
Subject: Re: disallow LOCK on a view - the Tom Lane remix

pgsql-patches by date

Next:From: Alfred PerlsteinDate: 2000-08-30 00:23:02
Subject: Re: disallow LOCK on a view - the Tom Lane remix
Previous:From: Alfred PerlsteinDate: 2000-08-29 23:14:00
Subject: Re: disallow LOCK on a view - the Tom Lane remix

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