From: | Mark Hollomon <mhh(at)mindspring(dot)com> |
---|---|
To: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: disallow LOCK on a view - the Tom Lane remix |
Date: | 2000-08-30 01:03:00 |
Message-ID: | 20000829210300.B25366@mindspring.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Tue, Aug 29, 2000 at 04:14:00PM -0700, Alfred Perlstein wrote:
>
> Ok, I'm wondering if this patch will cause problems locking a table
> that has had:
>
> CREATE RULE "_RETfoo" AS ON SELECT TO foo DO INSTEAD SELECT * FROM foo1;
>
> I need to be able to lock the table 'foo' exclusively while I swap
> out the underlying rule to forward to another table.
>
Yes, it would. 'foo' would be seen as view.
Okay, this gives me a reason to to do it the hard way.
I will try to add a relisview attribute to pg_class.
That way, we can differentiate between tables with rules
and things created with 'CREATE VIEW'.
Hmmm... guess I'll need to change the definition of the pg_views
view as well.
--
Mark Hollomon
mhh(at)mindspring(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-08-30 03:52:28 | Re: [HACKERS] disallow LOCK on a view - the Tom Lane remix |
Previous Message | Alfred Perlstein | 2000-08-30 00:23:02 | Re: disallow LOCK on a view - the Tom Lane remix |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-08-30 03:52:28 | Re: [HACKERS] disallow LOCK on a view - the Tom Lane remix |
Previous Message | Alfred Perlstein | 2000-08-30 00:23:02 | Re: disallow LOCK on a view - the Tom Lane remix |