Resent-Date: Mon, 27 Feb 2017 14:10:12 +0000
Resent-Message-Id: <E1ciM0C-00078o-MD@malur.postgresql.org>
From: Michael Banck <michael.banck@credativ.de>
To: Jim Nasby <Jim.Nasby@BlueTreble.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Pg Hackers
 <pgsql-hackers@postgresql.org>, Kevin Grittner <kgrittn@gmail.com>
Message-ID: <20170227135442.GD7222@nighthawk.caipicrew.dd-dns.de>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <65049c27-96bf-317b-b435-931f6041f94c@BlueTreble.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: Re: Change in "policy" on dump ordering?
Resent-From: Michael Banck <michael.banck@credativ.de>
Resent-To: PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: Mon, 27 Feb 2017 15:09:29 +0100
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Hi,

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

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-608582a8c4=
8d%402ndquadrant.com
you (Peter) wrote:=20

"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."
=20
> Patches for head attached.

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


Michael

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

credativ GmbH, HRB M=F6nchengladbach 12080
USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 M=F6nchengladbach
Gesch=E4ftsf=FChrung: Dr. Michael Meskes, J=F6rg Folz, Sascha Heuer


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