Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kBdek-0000bq-Iq for pgsql-hackers@arkaria.postgresql.org; Fri, 28 Aug 2020 12:38:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kBdej-0001TV-4n for pgsql-hackers@arkaria.postgresql.org; Fri, 28 Aug 2020 12:38:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kBdei-0001TO-Td for pgsql-hackers@lists.postgresql.org; Fri, 28 Aug 2020 12:38:56 +0000 Received: from tamriel.snowman.net ([96.255.250.162]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kBdec-0002Q7-C9 for pgsql-hackers@lists.postgresql.org; Fri, 28 Aug 2020 12:38:56 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 197B55F79F; Fri, 28 Aug 2020 08:38:48 -0400 (EDT) Date: Fri, 28 Aug 2020 08:38:48 -0400 From: Stephen Frost To: Magnus Hagander Cc: PostgreSQL Developers Subject: Re: New default role- 'pg_read_all_data' Message-ID: <20200828123847.GV29590@tamriel.snowman.net> References: <20200828003023.GU29590@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="OqUbWRofJmLkzr3q" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --OqUbWRofJmLkzr3q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greetings, * Magnus Hagander (magnus@hagander.net) wrote: > Without having actually looked at the code, definite +1 for this feature. > It's much requested... Thanks. > But, should we also have a pg_write_all_data to go along with it? Perhaps, but could certainly be a different patch, and it'd need to be better defined, it seems to me... read_all is pretty straight-forward (the general goal being "make pg_dumpall/pg_dump work"), what would write mean? INSERT? DELETE? TRUNCATE? ALTER TABLE? System catalogs? Doesn't seem like you could just declare it to be 'allow pg_restore' either, as that might include creating untrusted functions, et al. Thanks, Stephen --OqUbWRofJmLkzr3q Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJfSPrXAAoJEO1sijiDR2RVx5EQAJcXbu0JSB9AvJRe4oPaDv6a mWMUN3Vimzc3N6yGtYw+k0WOBCoImGT+FC3hpX6tmZ3fnnQZ9z4KwotXeUtE+amj U5ylIRk3xR2LbO0OF7JCCkZiVREKyQjRpy23osOO/4GdEIRYwGKCFGp+C0MsCgTh GrNpPikyEK+or7vE6ECzg5d0TY1fdFRwHhZZFaHaLOjbYLTZwX2VLG4uqeQXWZup Gp6MMLuDEpGhbzwxN5e1V/dpF/6wWdXX4+yVuxi8ef4BVBkKHEbWt0GiJ/Yx8ZVY EB3a05NcFNLScuCoUSlL3YQ+kh7MV5rroaoXIZnKUuECKDIJmBVvr4CZ5MmqxO3L mLQNbSOA/dfc5RQdnt4tMVOLFZ7Uwg5Eg/IvBGLLOg1UgFeujKyNBreC6S/2962q XySAuh6ljrmzmQ/XOQbJDIMLx9XO/GCo1jfowOP5k+dlqspWjV+ZmAkcuFHcVBJG B6yfOvEcnxvUJV8Uz5wcQBpsbLlucxRtsZvdCn8N40dAv3g0ojpGtxj4ErGgxG6F r5wlnomm2p8/tX7pGisHP6oBNCe/eGz6azm2p9YMX8FbrSiT81/X6SKoutJCvmva 8ODlsDGosMyNVTUdLguqorWkMmaID4gkzRROquLj1eKqkGnRDsYGx6e6Q2ZrFYrh CVhX629CShFe+wg9lLEE =WFmU -----END PGP SIGNATURE----- --OqUbWRofJmLkzr3q--