Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cggV5-0007dX-EE for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Feb 2017 23:39:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cggV5-0006dJ-19 for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Feb 2017 23:39:11 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cggTf-0004nb-Dl for pgsql-hackers@postgresql.org; Wed, 22 Feb 2017 23:37:43 +0000 Received: from tamriel.snowman.net ([2001:4830:167b::11]) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cggTc-0000zw-W0 for pgsql-hackers@postgresql.org; Wed, 22 Feb 2017 23:37:42 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 639C75F794; Wed, 22 Feb 2017 18:37:10 -0500 (EST) Date: Wed, 22 Feb 2017 18:37:10 -0500 From: Stephen Frost To: Jim Nasby Cc: Peter Eisentraut , Pg Hackers Subject: Re: Change in "policy" on dump ordering? Message-ID: <20170222233710.GR9812@tamriel.snowman.net> References: <87866740-ef55-8a6d-6480-499b92aa23c0@BlueTreble.com> <8f64786e-824d-7c0d-33a6-3d9e1c8e9fde@2ndquadrant.com> <33b25c65-94f1-6ff6-c717-61a56294a255@2ndquadrant.com> <75409fb1-bd96-25c2-f6b0-c24e28ed2684@2ndquadrant.com> <65049c27-96bf-317b-b435-931f6041f94c@BlueTreble.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dXjkapTmOFeqqigw" Content-Disposition: inline In-Reply-To: <65049c27-96bf-317b-b435-931f6041f94c@BlueTreble.com> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/3.13.0-91-generic (x86_64) X-Uptime: 18:35:19 up 229 days, 59 min, 12 users, load average: 0.13, 0.11, 0.14 User-Agent: Mutt/1.5.21 (2010-09-15) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org --dXjkapTmOFeqqigw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > Patches for head attached. >=20 > 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 --dXjkapTmOFeqqigw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJYriCmAAoJEO1sijiDR2RVMtsP/1yLcfzJPJ7NpAgwu6p7RHC+ IO9fT02xa/zRl8h2+brpM6tNwwMTxhPLTnU1Ss9IgIPyoKJWBujV83lSyHWFZT/Q qDBSLDnugpLAe6OSSqcSUJUDmbzXOGVeK3kOp4Occx+mFP1UyllGwSR1YIJUiinT 0MSJPmJUA3zqhcDrAT2AEGTzfb7iG77AkK0/J8q2WDilTjBYYGclwkgUj5qRVS9A CdXH3yg1SSpIUldigsaDQTt/4Db7FqxSXHjeb+8KGa0ltdlvaEGloiOSWkCbmiLl +Wlcf83vdhipuFyrz+1aWWn6hOtgXUv3gINRO5xWsi8I41Yj36jeYv13o9fbVeYZ vYR0Ipy2vpyhmSh8WLwRZSnGnzgNYu1nu6b5yf08jVBIrqYNNfpb7WX9CdZCeMyX AtBZzKyNlJVrZ6QZFZtqLbgwp08M/fCiCVeGlF9DH6wH8KYERYrmyOvGZUytvaTy U5ePrXjzRv178jlTtpVyTSJIq72/LDmeHd1ryuf5hrvSiFfe4ag/RKep50O1B2i8 IW+m1VUqkx7gMcsVahgoZ8tsQwmyGEo4gRhdWJYmPINAZDiaRwYr4yoncpK+qCvM +oUPuxKg7K3dKZxr/op6ZHXU4LJDXqBzbZliq1Bq38meeF3XtnrUYmDp++dQO65R 3Y5JnVm/8haYhRaEAQDx =EY8P -----END PGP SIGNATURE----- --dXjkapTmOFeqqigw--