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

From Jim Nasby
Subject Re: [HACKERS] Change in "policy" on dump ordering?
Date
Msg-id a537995b-ccdb-f668-5f67-98e9b9b4a99d@BlueTreble.com
Whole thread Raw
In response to Re: [HACKERS] Change in "policy" on dump ordering?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Change in "policy" on dump ordering?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 2/22/17 8:00 AM, Peter Eisentraut wrote:
>> Actually, I think matviews really need to be the absolute last thing.
>> What if you had a matview that referenced publications or subscriptions?
>> I'm guessing that would be broken right now.
> I'm not sure what you have in mind here.  Publications and subscriptions
> don't interact with materialized views, so the relative order doesn't
> really matter.

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.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [HACKERS] Make subquery alias optional in FROM clause
Next
From: "David G. Johnston"
Date:
Subject: Re: [HACKERS] Make subquery alias optional in FROM clause