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

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

From: "Mark Hollomon" <mhh(at)nortelnetworks(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alfred Perlstein <bright(at)wintelcom(dot)net>, Mark Hollomon <mhh(at)mindspring(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: disallow LOCK on a view - the Tom Lane remix
Date: 2000-08-30 12:18:02
Message-ID: 39ACFB7A.CCA577ED@americasm01.nt.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Tom Lane wrote:
> 
> BTW, this seems to be a counterexample for my prior suggestion that
> pg_class should have a "relviewrule" OID column.  If it did, you'd
> have to update that field when doing something like the above.
> Pain-in-the-neck factor looms large...
> 

I was already considering the possiblity of a 'ALTER VIEW' command that
would effectively allow you do that.

CREATE VIEW bar as select * from foo1;
ALTER VIEW bar as select * from foo2;

It would update the "relviewrule" field.
-- 

Mark Hollomon
mhh(at)nortelnetworks(dot)com
ESN 451-9008 (302)454-9008

In response to

pgsql-hackers by date

Next:From: Mark HollomonDate: 2000-08-30 12:31:10
Subject: Re: Backend-internal SPI operations
Previous:From: Jan WieckDate: 2000-08-30 11:52:37
Subject: Re: Backend-internal SPI operations

pgsql-patches by date

Next:From: Mark HollomonDate: 2000-08-30 12:31:10
Subject: Re: Backend-internal SPI operations
Previous:From: Jan WieckDate: 2000-08-30 11:52:37
Subject: Re: Backend-internal SPI operations

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