Re: BUG #14147: Restore of MatView of Foreign Data Table fails - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: BUG #14147: Restore of MatView of Foreign Data Table fails
Date
Msg-id CACjxUsOehDmcRQLvaJ50c_5E6_u5mG=wBAuPaLgtnPVjF97r9A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14147: Restore of MatView of Foreign Data Table fails  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Mon, May 23, 2016 at 2:07 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> lalbin@scharp.org writes:
>> I have found that restoration of Materialized Views of Foreign Data Tables
>> where user postgres does not have a user mapping will fail. It seems that it
>> is trying to execute the Foreign Data Table in some way instead of reading
>> the Foreign Table Definition.
>
> This is another variant of a problem that's been complained of multiple
> times before: CREATE MATERIALIZED VIEW ... WITH NO DATA runs planning and
> even does ExecutorStart for the view's query, causing issues such as lack
> of permissions to be exposed.  This breaks assorted assumptions in pg_dump
> and probably other places.  We need to refactor things so that that does
> not happen.  Kevin, are you planning to fix that anytime soon?

I'll move this to the top of my list after dealing with any 9.6 issues
that come up.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #14147: Restore of MatView of Foreign Data Table fails
Next
From: digoal@126.com
Date:
Subject: BUG #14155: bloom index error with unlogged table