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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-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

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Hollomon 2000-08-30 12:31:10 Re: Backend-internal SPI operations
Previous Message Jan Wieck 2000-08-30 11:52:37 Re: Backend-internal SPI operations

Browse pgsql-patches by date

  From Date Subject
Next Message Mark Hollomon 2000-08-30 12:31:10 Re: Backend-internal SPI operations
Previous Message Jan Wieck 2000-08-30 11:52:37 Re: Backend-internal SPI operations