pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Michael Banck <michael.banck@credativ.de>
To: Jim Nasby <Jim.Nasby@BlueTreble.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Cc: Kevin Grittner <kgrittn@gmail.com>
Subject: Re: Change in "policy" on dump ordering?
Date: Mon, 27 Feb 2017 15:09:29 +0100
Message-ID: <20170227135442.GD7222@nighthawk.caipicrew.dd-dns.de> (raw)
In-Reply-To: <65049c27-96bf-317b-b435-931f6041f94c@BlueTreble.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>
	<a537995b-ccdb-f668-5f67-98e9b9b4a99d@BlueTreble.com>
	<75409fb1-bd96-25c2-f6b0-c24e28ed2684@2ndquadrant.com>
	<65049c27-96bf-317b-b435-931f6041f94c@BlueTreble.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Hi,

I've found the (AIUI) previous discussion about this, it's Bug #13907:
https://www.postgresql.org/message-id/flat/20160202161407.2778.24659%40wrigleys.postgresql.org#20160...

On Wed, Feb 22, 2017 at 05:24:49PM -0600, Jim Nasby wrote:
> On 2/22/17 12:29 PM, Peter Eisentraut wrote:
> >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.

In https://www.postgresql.org/message-id/9af4bc32-7e55-a21d-47e7-608582a8c48d%402ndquadrant.com
you (Peter) wrote: 

"The reason that ACLs are restored last is that they could contain owner
self-revokes.  So anything that you run after the ACLs could fail
because of that.  I think a more complete fix would be to split up the
ACL restores into the general part, which you would run right after the
object is restored, and the owner revokes, which you would run last."
 
> Patches for head attached.

FWIW, Keven Grittner had proposed a more involved patch in 
https://www.postgresql.org/message-id/CACjxUsNmpQDL58zRm3EFS9atqGT8%2BX_2%2BFOCXpYBwWZw5wgi-A%40mail...


Michael

-- 
Michael Banck
Projektleiter / Senior Berater
Tel.: +49 2166 9901-171
Fax:  +49 2166 9901-100
Email: michael.banck@credativ.de

credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer




-- 
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: <20170227135442.GD7222@nighthawk.caipicrew.dd-dns.de>
Permalink:  ../20170227135442.GD7222@nighthawk.caipicrew.dd-dns.de/
Also on:    postgresql.org/message-id/20170227135442.GD7222@nighthawk.caipicrew.dd-dns.de

 · 

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: michael.banck@credativ.de, Jim.Nasby@BlueTreble.com, peter.eisentraut@2ndquadrant.com, kgrittn@gmail.com
  Subject: Re: Change in "policy" on dump ordering?
  In-Reply-To: <20170227135442.GD7222@nighthawk.caipicrew.dd-dns.de>

* 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