Re: [HACKERS] Change in "policy" on dump ordering? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Change in "policy" on dump ordering?
Date
Msg-id 75409fb1-bd96-25c2-f6b0-c24e28ed2684@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Change in "policy" on dump ordering?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: [HACKERS] Change in "policy" on dump ordering?
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: [HACKERS] Note about bug #14563
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] [PROPOSAL] Temporal query processing with range types