pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Change in "policy" on dump ordering?
Date: Wed, 22 Feb 2017 09:14:56 -0600
Message-ID: <a537995b-ccdb-f668-5f67-98e9b9b4a99d@BlueTreble.com> (raw)
In-Reply-To: <33b25c65-94f1-6ff6-c717-61a56294a255@2ndquadrant.com>
References: <87866740-ef55-8a6d-6480-499b92aa23c0@BlueTreble.com>
	<8f64786e-824d-7c0d-33a6-3d9e1c8e9fde@2ndquadrant.com>
	<edc1dc0d-66ba-0d9e-b0e7-890f064789d7@BlueTreble.com>
	<33b25c65-94f1-6ff6-c717-61a56294a255@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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)


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (29+ messages)  latest in thread

Message-ID: <a537995b-ccdb-f668-5f67-98e9b9b4a99d@BlueTreble.com>
Permalink:  ../a537995b-ccdb-f668-5f67-98e9b9b4a99d@BlueTreble.com/
Also on:    postgresql.org/message-id/a537995b-ccdb-f668-5f67-98e9b9b4a99d@BlueTreble.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: Jim.Nasby@BlueTreble.com, peter.eisentraut@2ndquadrant.com
  Subject: Re: Change in "policy" on dump ordering?
  In-Reply-To: <a537995b-ccdb-f668-5f67-98e9b9b4a99d@BlueTreble.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox