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

On Tue, Feb 2, 2016 at 7:14 PM, <marian(dot)krucina(at)gmail(dot)com> wrote:
> restore (9.4.5, 9.5.0) or pg_upgrade (9.4.5 to 9.5.0) fail on CREATE
> MATERIALIZED VIEW.
> This is similar to:
> http://www.postgresql.org/message-id/11166.1424357659@sss.pgh.pa.us
>
> Problem is, when view runs as user definer.
> Is possible move 'CREATE MATERIALIZED VIEW' in a dump to end?

This is one of those issues where it would be cool to only plan and
execute the query creating the materialized view query with NO DATA
without planning and executing it first, and do the actual planning
and execution at the first refresh. A similar problem was discussed
here:
https://www.postgresql.org/message-id/flat/20160115175546(dot)2968(dot)6033%40wrigleys(dot)postgresql(dot)org#20160115175546(dot)2968(dot)6033(at)wrigleys(dot)postgresql(dot)org

Thought I don't think that it is that straight-forward, the relation
defined using a CTAS uses column information directly derived from the
query planned, so the fix would be to extract the necessary
information for those columns: collation, column name, type OID and
typemod without the need of the existing routines.
--
Michael