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 1kD8xp-0000o1-9Z for pgsql-bugs@arkaria.postgresql.org; Tue, 01 Sep 2020 16:16:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kD8xo-00011S-7M for pgsql-bugs@arkaria.postgresql.org; Tue, 01 Sep 2020 16:16:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kD8xn-00011L-TA for pgsql-bugs@lists.postgresql.org; Tue, 01 Sep 2020 16:16:51 +0000 Received: from tamriel.snowman.net ([96.255.250.162]) by makus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kD8xl-0001Lx-N6 for pgsql-bugs@lists.postgresql.org; Tue, 01 Sep 2020 16:16:50 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 082F35F79F; Tue, 1 Sep 2020 12:16:48 -0400 (EDT) Date: Tue, 1 Sep 2020 12:16:48 -0400 From: Stephen Frost To: yuri6037@outlook.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16603: Permission issue Message-ID: <20200901161648.GW29590@tamriel.snowman.net> References: <16603-40b468dea6a57650@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2uNvYoNvpSuZzx5w" Content-Disposition: inline In-Reply-To: <16603-40b468dea6a57650@postgresql.org> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --2uNvYoNvpSuZzx5w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greetings, * PG Bug reporting form (noreply@postgresql.org) wrote: > The following MySQL query: GRANT ALL PRIVILEGES ON database_name.* TO > 'username'@'localhost'; allows one to assign one database to a given user. > That includes ALL permissions even database creation. > Currently this behavior is impossible in PostgreSQL: One can create a > database and GRANT ALL PRIVILEGES however this won't grant the CREATEDB > permission on that database. The bug/issue here is that CREATEDB cannot be > assigned to a specific database/user combination. No, it's not currently possible to GRANT access to objects that don't exist in PG. This isn't a bug, as for if it's a possible future feature, maybe (there's a current patch that I'm working on to GRANT things like 'read only' or 'write only' access to all tables/views/etc), but I don't expect to ever support the ability for GRANT to explicitly name an object that doesn't exist yet (seems like it'd be rather concerning too, because what if someone *else* created that database? Suddenly this user has access to it? No, thanks). > Currently this bug prevents development of some applications. As such in one > of my application I was forced to drop support for PostgreSQL and return to > MySQL. This hasn't ever worked in PG, so it seems a little curious that it's the cause for PG support to be dropped. Still, it's definitely not a bug and certainly wouldn't be added to existing releases. If you're interested in following the development of PG, I'd suggest you take a look at the -hackers mailing list. Thanks, Stephen --2uNvYoNvpSuZzx5w Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJfTnPwAAoJEO1sijiDR2RV840P/RiaMbksw7CRIbxs+VePQnDQ UFQJWPNuldZvke42RSsSGvQnffQLnTI6bNEYXaj5aVbwbYKWb9ooyTSm8HQIddOM CIP2jnqT7+mCxfqflsjz9ZpahVsbAr+xdwRiGJ39OzZAOfSdYj6wBJ8fSFDcELmC SyES26Irq4qq4+COcTHLekFn68kZSIGAMCXizYqaCGvr7/h8HrAB+zrB/ZuU4rkL uWfWMWMBf+pYP8IJSqlHHcexxc6pCz+dhcB8OW7FGFEGxRDC60M6fqqLWRuSYLF6 F42XPoyRDFc6C0Kd5e+Ie8dLQhR+MKSWE1E4vGqPY8HEe4u3f9iM+7jqOViU0r15 lg3K5RXWSpYgLiGPGKKauoz1gJZmUF13YgDPzSHDADxK+qTINU+szbZOZrrMYw3C VEuqZUDVD7DwMLV3pDI0RuEL53S0uOuJAq9N4mwMC3YYLD2WkSZBlaClzFEKAS0N H/LJ8TQ4h20XoJVaNwB6+AeqAzmsMNGJb4YdCn5CmiSrfuY8iWaPpO7uD8LBX29n OS0U3etoJGSDL5cZWTQ8QgZNDUM7q+WhNwKhF+l88iP702SITLZDVp9asA8gPgdi Q6GalTVRWcMsGwR4m8nyloZvaF9vW1wvXuKE9V55NO5iljoVu/vjKHeuJoDOzKsa JoY/Esb7L48VkiozI2Mv =UWlm -----END PGP SIGNATURE----- --2uNvYoNvpSuZzx5w--