From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proof of concept: auto updatable views |
Date: | 2012-09-02 20:37:40 |
Message-ID: | CAEZATCXX04uUkK6=BCSZAwd3xunzYfyid4itGHTcz3cg_y1TtA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 31 August 2012 07:59, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
> On 30 August 2012 20:05, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Sun, Aug 12, 2012 at 5:14 PM, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
>>> None of this new code kicks in for non-security barrier views, so the
>>> kinds of plans I posted upthread remain unchanged in that case. But
>>> now a significant fraction of the patch is code added to handle
>>> security barrier views. Of course we could simply say that such views
>>> aren't updatable, but that seems like an annoying limitation if there
>>> is a feasible way round it.
>>
>> Maybe it'd be a good idea to split this into two patches: the first
>> could implement the feature but exclude security_barrier views, and
>> the second could lift that restriction.
>>
>
> Yes, I think that makes sense.
> I should hopefully get some time to look at it over the weekend.
>
Here's an updated patch for the base feature (without support for
security barrier views) with updated docs and regression tests.
Regards,
Dean
Attachment | Content-Type | Size |
---|---|---|
auto-update-views.patch.gz | application/x-gzip | 14.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2012-09-02 21:39:22 | Re: [v9.3] Row-Level Security |
Previous Message | Bruce Momjian | 2012-09-02 20:09:28 | Re: Yet another failure mode in pg_upgrade |