Re: BUG #13870: couldn't restore dump with mat view
От | Michael Paquier |
---|---|
Тема | Re: BUG #13870: couldn't restore dump with mat view |
Дата | |
Msg-id | CAB7nPqTLChjV1GVt4wwz5N6mwpDNJGFSFfpr0Qasoi+a-Z314Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #13870: couldn't restore dump with mat view (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #13870: couldn't restore dump with mat view
|
Список | 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 по дате отправления: