From: Stephen Frost <sfrost@snowman.net>
To: Jim Nasby <Jim.Nasby@BlueTreble.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Change in "policy" on dump ordering?
Date: Wed, 22 Feb 2017 18:37:10 -0500
Message-ID: <20170222233710.GR9812@tamriel.snowman.net> (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>
Jim,
* Jim Nasby (Jim.Nasby@BlueTreble.com) 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.
>
> Patches for head attached.
>
> RLS was the first item added after DO_REFRESH_MATVIEW, which was
> added in 9.5. So if we want to treat this as a bug, they'd need to
> be patched as well, which is a simple matter of swapping 33 and 34.
Can you clarify what misbehavior there is with RLS that would warrent
this being a bug..? I did consider where in the dump I thought policies
should go, though I may certainly have overlooked something.
Thanks!
Stephen
Attachments:
[application/pgp-signature] signature.asc (818B, ../20170222233710.GR9812@tamriel.snowman.net/2-signature.asc)
download
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: sfrost@snowman.net, Jim.Nasby@BlueTreble.com, peter.eisentraut@2ndquadrant.com
Subject: Re: Change in "policy" on dump ordering?
In-Reply-To: <20170222233710.GR9812@tamriel.snowman.net>
* 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