Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cdJzA-0006k6-RA for pgsql-general@arkaria.postgresql.org; Mon, 13 Feb 2017 17:00:20 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cdJz9-0003kU-Px for pgsql-general@arkaria.postgresql.org; Mon, 13 Feb 2017 17:00:19 +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 1cdJwq-0000OO-F6 for pgsql-general@postgresql.org; Mon, 13 Feb 2017 16:57:56 +0000 Received: from tamriel.snowman.net ([2001:4830:167b::11]) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cdJwn-0008Nn-TI for pgsql-general@postgresql.org; Mon, 13 Feb 2017 16:57:54 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 6CA415F794; Mon, 13 Feb 2017 11:57:53 -0500 (EST) Date: Mon, 13 Feb 2017 11:57:53 -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: <20170213165753.GR9812@tamriel.snowman.net> References: <3534542.o3cNaKiDID@techfox> <23252987.YLsmlhlehZ@techfox> <20170213141042.GJ9812@tamriel.snowman.net> <2623240.ZhDaCM8aGs@techfox> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="uJfGEQrtd68Y1uyR" Content-Disposition: inline In-Reply-To: <2623240.ZhDaCM8aGs@techfox> 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: 11:57:04 up 219 days, 18:21, 11 users, load average: 0.22, 0.17, 0.21 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 --uJfGEQrtd68Y1uyR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Frank, * 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' use= =20 > tables in various schema's, it was actually the one 'older' db with every= thing=20 > in the public schema that brought it up, so maybe keeping one of those ar= ound=20 > isn't too bad an idea ;) 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. Thanks! Stephen --uJfGEQrtd68Y1uyR Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJYoeWRAAoJEO1sijiDR2RVVqAP/j7h5DusXwhSNuk4cytnWwxi OPvdsgQWfOWdzF4DmkUcrXs3nC6HMW3VTrajFrdfibGz57UEeQqKtfSVNCaSyzLE 42S4L29ivN0nu8bvi36Phqt4mD+S3wCV1hd5w/gGazJCrN9SJeTBVyv3N1rqTnTD F1CftMt6zfrE+2olfcuarwBYK9Sf8aJQCXb0TX/K0fHWcCut7HcKfR2kZoIBrlqs dGCvql8xCbbDHJ8TohcUbAepaH84XX3VhxW6G8caI+6U7+YGJA67ndmwCcxxgvUd 8Sy+NSYxVUHI8yvl/jyYz47vIdbRq69kcGWIRvcF2SO4xS/BDQjL8uIL0m3UI12x cXnekk3ill937kEebnkWH0sSOxUgRBMpHBD101mn8F3SOGMoHSPHN6KusGlYv7o8 kT2jVKHeHJKmQNZwsxGlw+LNATxpX88oK9JCKIPXbWY1KJ8o2n7nGOJgqfTqKmqU zm/Y5+31uCQVLmdrQSlSe/0A3CV31UXN0mjhdDp7jdEayzFvwcdRH6/BUa3STHvh fDFbOU/m3LTBFuyj3+3DEmnKsm6y5YpijUHfEC9Pzt+rlZ4N936NboYCUoOqGD93 Fw/TCVNuMNNou2do1vySOk8ZjEmrA10jADoI0B/CDNsLYnEM5lXq4J2xrtj6LVB3 30U0Wx6Iom42epEvStfH =LAgH -----END PGP SIGNATURE----- --uJfGEQrtd68Y1uyR--