Re: BUG #13870: couldn't restore dump with mat view - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #13870: couldn't restore dump with mat view
Date
Msg-id CAB7nPqTLChjV1GVt4wwz5N6mwpDNJGFSFfpr0Qasoi+a-Z314Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13870: couldn't restore dump with mat view  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #13870: couldn't restore dump with mat view
List pgsql-bugs
On Sat, Jan 16, 2016 at 10:58 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> kardash.a.v@yandex.ru writes:
>> Try to feed sql-commands below, then do dump and you will see errors while
>> restore!
>
> Well, this example doesn't work as-is because the command order is already
> wrong.  But the issue is that CREATE MATERIALIZED VIEW ... WITH NO DATA
> tries to plan and execute the query, not just store it, which entirely
> defeats pg_dump's attempt to avoid hidden dependencies.  We need a less
> chintzy solution to handling this variant of CREATE MATERIALIZED VIEW.
>
> (I seem to recall complaining about this before.)

The first issue in the dump is the creation of point(), which depends
on relation stend.
--
Michael

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #13870: couldn't restore dump with mat view
Next
From: Michael Paquier
Date:
Subject: Re: [BUGS] about test_parser installation failure problem(PostgreSQL in 9.5.0)?