Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qNwFO-006Nvc-Hl for pgsql-general@arkaria.postgresql.org; Mon, 24 Jul 2023 14:09:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qNwFN-00AwC4-42 for pgsql-general@arkaria.postgresql.org; Mon, 24 Jul 2023 14:09:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qNwFM-00AwBw-Pz for pgsql-general@lists.postgresql.org; Mon, 24 Jul 2023 14:09:12 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qNwFK-0001bX-BZ for pgsql-general@lists.postgresql.org; Mon, 24 Jul 2023 14:09:12 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 36OE966x1549850; Mon, 24 Jul 2023 10:09:06 -0400 From: Tom Lane To: "David G. Johnston" cc: Kaushal Shriyan , Ron , "pgsql-general@lists.postgresql.org" Subject: Re: Grant all privileges to user on a database In-reply-to: References: <85b5b466-1efd-fb89-8686-08e5df88a00b@gmail.com> Comments: In-reply-to "David G. Johnston" message dated "Mon, 24 Jul 2023 06:56:28 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1549848.1690207746.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Mon, 24 Jul 2023 10:09:06 -0400 Message-ID: <1549849.1690207746@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > The error message is misleading, you can’t directly create tables in a > database, you must create them in a schema and the permission to do so is > granted to the role on the schema, not the database. The actual server message is going to be just ERROR: permission denied for schema public I'm not sure where the "Are you sure ..." bit came from, but it wasn't Postgres. Anyway, backing up two steps, it looks like drupal hasn't yet adapted to the v15 change that removed default create privileges on the public schema (for security reasons). You might see if a newer drupal release is available. If not, the best bet would likely be GRANT ALL ON SCHEMA public TO public; If you run into more problems, a more drastic answer might be to downgrade to whatever drupal considers a supported release of Postgres. regards, tom lane