Re: BUG #13907: Restore materialized view throw permission denied

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: marian(dot)krucina(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13907: Restore materialized view throw permission denied
Date: 2016-06-15 07:37:12
Message-ID: CAB7nPqTVtZ0vWUSa4sQUFSZvkp0xacw2oojmhYSwi85SP45d9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jun 14, 2016 at 10:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Gabriele Monfardini 2016-06-15 07:45:13 Re: BUG #14188: "FOR SELECT DISTINCT, ORDER BY expressions must appear IN SELECT list" error and table alias
Previous Message digoal 2016-06-15 05:47:52 BUG #14191: plpgsql run infinit when i use bulk query first time