Re: BUG #13907: Restore materialized view throw permission denied - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #13907: Restore materialized view throw permission denied
Date
Msg-id CAB7nPqTVtZ0vWUSa4sQUFSZvkp0xacw2oojmhYSwi85SP45d9w@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13907: Restore materialized view throw permission denied  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #13907: Restore materialized view throw permission denied  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
On Tue, Jun 14, 2016 at 10:29 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I think you want to be looking at the way that CREATE VIEW accomplishes
> the same task.  See DefineView and DefineVirtualRelation.  It might be
> worth refactoring those a bit to allow code sharing.

Ah, right! I forgot that views already solve this problem in its way,
and that's definitely something that we should do.

[code lookup]

OK I see now how to wrap that. I'll come up with something that can be
back-patched and think about the refactoring carefully.
--
Michael

pgsql-bugs by date:

Previous
From: digoal@126.com
Date:
Subject: BUG #14191: plpgsql run infinit when i use bulk query first time
Next
From: Gabriele Monfardini
Date:
Subject: Re: BUG #14188: "FOR SELECT DISTINCT, ORDER BY expressions must appear IN SELECT list" error and table alias