Re: Change in "policy" on dump ordering?

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Change in "policy" on dump ordering?
Date: 2017-02-22 18:29:18
Message-ID: 75409fb1-bd96-25c2-f6b0-c24e28ed2684@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/22/17 10:14, Jim Nasby wrote:
> CREATE MATERIALIZED VIEW tmv AS SELECT * FROM pg_subscription;
> SELECT 0
>
> IOW, you can create matviews that depend on any other
> table/view/matview, but right now if the matview includes certain items
> it will mysteriously end up empty post-restore.

Yes, by that logic matview refresh should always be last.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-02-22 18:43:38 Re: [PROPOSAL] Temporal query processing with range types
Previous Message Tom Lane 2017-02-22 18:19:54 Note about bug #14563