Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1clGDu-0000SQ-3C for pgsql-general@arkaria.postgresql.org; Tue, 07 Mar 2017 14:36:22 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1clGDt-0006sT-Kt for pgsql-general@arkaria.postgresql.org; Tue, 07 Mar 2017 14:36:21 +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 1clGBT-0002Ty-Ay for pgsql-general@postgresql.org; Tue, 07 Mar 2017 14:33:51 +0000 Received: from tamriel.snowman.net ([72.66.115.51]) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1clGBO-0004Em-Cm for pgsql-general@postgresql.org; Tue, 07 Mar 2017 14:33:49 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id B8BA35F79F; Tue, 7 Mar 2017 09:32:45 -0500 (EST) Date: Tue, 7 Mar 2017 09:32:45 -0500 From: Stephen Frost To: Frank van Vugt Cc: pgsql-general@postgresql.org Subject: Re: intentional or oversight? pg_dump -c does not restore default priviliges on schema public Message-ID: <20170307143245.GI9812@tamriel.snowman.net> References: <3534542.o3cNaKiDID@techfox> <23252987.YLsmlhlehZ@techfox> <20170213141042.GJ9812@tamriel.snowman.net> <2623240.ZhDaCM8aGs@techfox> <20170213165753.GR9812@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="o/NWWBMRgqVrTAcB" Content-Disposition: inline In-Reply-To: <20170213165753.GR9812@tamriel.snowman.net> 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: 09:32:25 up 241 days, 15:56, 15 users, load average: 0.01, 0.04, 0.05 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-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org --o/NWWBMRgqVrTAcB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Stephen Frost (sfrost@snowman.net) wrote: > * Frank van Vugt (ftm.van.vugt@foxi.nl) wrote: > > Well, I didn't run into this issue with any of my db's that 'nicely' us= e=20 > > tables in various schema's, it was actually the one 'older' db with eve= rything=20 > > in the public schema that brought it up, so maybe keeping one of those = around=20 > > isn't too bad an idea ;) >=20 > Yeah, I'll be including this in a regression test also, to make sure we > don't end up breaking this special case again in the future. I've now pushed a fix for this, would be great to know if it solves your issue. Thanks! Stephen --o/NWWBMRgqVrTAcB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJYvsSNAAoJEO1sijiDR2RVNUsQAJShgfQ87X8aWQrxhYN1dL8h vdH4W7JWK1lJb8br+1/M45HewoX2tLaSFbnIR0eCeArF9yDeDzmfCZNOzD+PcGIt jSUP2aoBpoYJs2PWFsl55+tkVz0h3eUeZac34mY+KZ2vXiSU+7QAP4akg6MH84S0 /pQrUVweo7JY7E/Tep9Kj+FxuFOhfpIcPYhKhpPM5Mw1GdZ/4Qz16RDiK+U+U8Nm AVf8/NcWVwcSElaW4KKdXpl5JHOVcadAfJ9nWlyjWyjyut6SUSP+LtVPyBavHdtJ BZ8oTEBWO0ShTtIuvaM8Zaalh2akfZAOKiUQlxmAgLli3WGXIDttzJcx5HWX/mFW AFQq7+xokLtPZgB9SIoCOYG2BF3h/MVxMeNpgio6vKfYnYw9Anv/cHvNjQgj39rl iI5JbFTN9d51QjRDH/lrDeLwCY2iXpQHugapExtojgYSSKhcMgLwbVBrcqX7SVen NN/YdXTud7oqUJgrbsieomO63ZYJ3OKBaTC4/sPv1p6FwZRx+wPSD+xljO/7VNKP tq/Kv3/vR8c8U3WN8a/7UDBn3f/q5xYkw67JHnVZJhhakXBXrBGcXgoIcT3GcrQs j8sAuhiD03nd4/apJb9wtS2SPvBB1b6QLOk3MTYBXs/tD77p+1yOW4MAj8Z7ukaj GFAd/nVsj9gNT800q0Xs =VmP+ -----END PGP SIGNATURE----- --o/NWWBMRgqVrTAcB--