| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | lalbin(at)scharp(dot)org, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14147: Restore of MatView of Foreign Data Table fails |
| Date: | 2016-05-23 19:17:45 |
| Message-ID: | CACjxUsOehDmcRQLvaJ50c_5E6_u5mG=wBAuPaLgtnPVjF97r9A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, May 23, 2016 at 2:07 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> lalbin(at)scharp(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-05-23 19:22:07 | Re: Re: [BUGS] BUG #14153: Unrecognized node type error when upsert is present in recursive CTE |
| Previous Message | Tom Lane | 2016-05-23 19:07:21 | Re: BUG #14147: Restore of MatView of Foreign Data Table fails |