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 1qg8Iq-00EY1l-CO for pgsql-novice@arkaria.postgresql.org; Tue, 12 Sep 2023 18:40:00 +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 1qg8He-00A57p-L4 for pgsql-novice@arkaria.postgresql.org; Tue, 12 Sep 2023 18:38:46 +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 1qg8Hd-00A57b-MT for pgsql-novice@lists.postgresql.org; Tue, 12 Sep 2023 18:38:45 +0000 Received: from mx1.riseup.net ([198.252.153.129]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qg8HZ-004C30-Rz for pgsql-novice@lists.postgresql.org; Tue, 12 Sep 2023 18:38:43 +0000 Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4RlXP63B7yzDqvG for ; Tue, 12 Sep 2023 18:36:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1694543818; bh=3g3u8iwSbIeRpYmBGWLfwz99q2TwYMnQ+jXAMcBibOs=; h=Date:From:To:Subject:In-Reply-To:References:From; b=M6V5BmG+Mi/PubVaiHCSE+V+Kl62dcC/48SjYsCTebUm0oxHT/me7dvHjHFcQ+cFV Y2D7nyTiyUZ1hc71HbC2tvbmoG2zTE14KbXQfSlKfcbYdbph1B7P7WXKrXcSmLZ35o DSJ4HdZEEA43pH8+xMfxjrzAPwXx5Agk7gMC2LUs= X-Riseup-User-ID: BFBE3EFDDC16A97F33784CA703A1B247817BA0CB6C4EA12E4ACEA9EF18347E0B Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4RlXP628qrzFqjr for ; Tue, 12 Sep 2023 18:36:58 +0000 (UTC) MIME-Version: 1.0 Date: Tue, 12 Sep 2023 18:36:57 +0000 From: ivanov17@riseup.net To: Pgsql Novice Subject: Re: Grant CREATE privilege on all schemas In-Reply-To: <2712774.1694484281@sss.pgh.pa.us> References: <2712774.1694484281@sss.pgh.pa.us> Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Tom Lane писал(а) 2023-09-12 06:04: > ivanov17@riseup.net writes: >> Is there a way to grant roles CREATE >> privileges on all schemas? > > This is not supported, and it's not likely to ever become supported > in exactly the way you phrased it, because that would presumably > include CREATE on the pg_catalog schema. Oh, now I understand. I think that if something like this is ever implemented, system catalogs should not be accessible to such a role. > If you give somebody > that, you might as well just skip the fooling around and give them > full superuser, because they could hack their way to that in less > time than it's taking me to type this email. In general, you > want to be pretty darn chary about giving out permissions on > schemas that are likely to be in other users' search_path, for > much the same reasons that you don't give random users write > permission on /usr/bin/. Thank you very much, now it becomes clearer to me. -- With appreciation, Ivanov