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 1t8NZg-003poh-7W for pgsql-general@arkaria.postgresql.org; Tue, 05 Nov 2024 17:42:39 +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 1t8NZd-00GdPQ-3y for pgsql-general@arkaria.postgresql.org; Tue, 05 Nov 2024 17:42:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t8NZc-00GdPI-L0 for pgsql-general@lists.postgresql.org; Tue, 05 Nov 2024 17:42:37 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t8NZa-000L8J-GW for pgsql-general@lists.postgresql.org; Tue, 05 Nov 2024 17:42:35 +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 4A5HgWwW3070157; Tue, 5 Nov 2024 12:42:32 -0500 From: Tom Lane To: Dominique Devienne cc: pgsql-general@lists.postgresql.org Subject: Re: Switching to NOINHERIT user triggers #XX000 error In-reply-to: References: Comments: In-reply-to Dominique Devienne message dated "Tue, 05 Nov 2024 18:10:46 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3070155.1730828552.1@sss.pgh.pa.us> Date: Tue, 05 Nov 2024 12:42:32 -0500 Message-ID: <3070156.1730828552@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Dominique Devienne writes: > On v16 and v17 though, it works with INHERIT, but with NOINHERIT, I get: > GRANT "...:USER" TO "ddevienne" #XX000: ERROR: no possible grantors > Any clue to what this means, so I can start looking in the right place? \errverbose in psql would help you locate what part of the code is throwing that. (Or if triggering it from psql is not convenient, set log_error_verbosity = verbose and find the info in the postmaster log.) This is probably a bug, at least to the extent that we don't like XX000 errors to be easily reachable, so please let us know what you find out. regards, tom lane