| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | kardash(dot)a(dot)v(at)yandex(dot)ru, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Subject: | Re: BUG #13870: couldn't restore dump with mat view |
| Date: | 2016-01-16 06:01:02 |
| Message-ID: | CAB7nPqTLChjV1GVt4wwz5N6mwpDNJGFSFfpr0Qasoi+a-Z314Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Jan 16, 2016 at 10:58 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> kardash(dot)a(dot)v(at)yandex(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-01-16 06:02:50 | Re: [BUGS] about test_parser installation failure problem(PostgreSQL in 9.5.0)？ |
| Previous Message | Michael Paquier | 2016-01-16 05:57:50 | Re: BUG #13870: couldn't restore dump with mat view |