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 1oxET7-0000UO-OU for pgsql-general@arkaria.postgresql.org; Mon, 21 Nov 2022 21:36:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oxET6-0005i8-B0 for pgsql-general@arkaria.postgresql.org; Mon, 21 Nov 2022 21:36:44 +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 1oxET5-0005g4-58 for pgsql-general@lists.postgresql.org; Mon, 21 Nov 2022 21:36:43 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oxESy-0001up-2v for pgsql-general@lists.postgresql.org; Mon, 21 Nov 2022 21:36:42 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id EEBE15C004D; Mon, 21 Nov 2022 16:36:34 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 21 Nov 2022 16:36:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1669066594; x= 1669152994; bh=LLgpw6izcOtevurOjwTYu/0KEVwjS0liEpcNwHdkKT4=; b=h lzTEgzEP9RhIXvbrmWqEU4srxBpHP4fp5pLYb4f6P1SF5Vus4UzZZqj1oD/7Ggrm 42cTW1akGMRAgp5svz5LTV658d3NmB/8S0WI/RzIoU7NnKo1mG7/2xr+xJJ0rOYW CQi44B2zpl1jrsnA0Nz07xIF1c81BblDFa97hbNjNJScwJ+4gG/biuByuFqp5xvL H8h0J9CTM71m+nuI4N/DUqxoWRNeKDFv+RxoNMrFKP21Iu5wK4Xn4wBfAS8/TOgt R306fjoreXF7lEDRoVKW7M0yo6fBqdc2nZ3qdlF5eTf1D9pwTLPqy6AnPY+lB08l kCb55zGk2rodjUN1eIWCg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1669066594; x= 1669152994; bh=LLgpw6izcOtevurOjwTYu/0KEVwjS0liEpcNwHdkKT4=; b=P NMFD+rO7ca1m+A+b/NIRU/K/WdSbFj77DMxrH7aZ9VkNqWRLkb8gw/sUPDxX7lo8 thrF/iuxqQMT/5HuEJjGywST6vB9bdivBB32kHMgvggoUte9Bjs5ZwZBLtkZ8ATj L93EJcL1n9dQj2XEag+38+v899Q/fAUu0yEX0Q2joZN1eIBI7UEDpyAFQnCx6Xpp e2NwNGdMWmyneGM/rILGR2GW2SzgeUjEY0u1wnnczV+pv4jKYsmO4HZZ0Sg1kAMv MEaMrOA/NVrZtwwGRllXkBbLLAFgScOskpgStLVdO7cQ31Oy8C17oaaPLDFaU0wr NpSsYPcKBfk9xKyb513Ag== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrheeigdduheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhephedugfethfettdehieevteeukedtjedvhfevkefg udefgeevteduvdeuvdeggeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 21 Nov 2022 16:36:34 -0500 (EST) Message-ID: Date: Mon, 21 Nov 2022 13:36:33 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: Seeking practice recommendation: is there ever a use case to have two or more superusers? To: Bryn Llewellyn Cc: "David G. Johnston" , pgsql-general list References: <290EF7B8-D150-4AE1-8FFE-A38912CD1A8B@yugabyte.com> <20221118200835.sgva7b6wgg4w7py7@hjp.at> <0B653B38-2D7D-45D6-B87F-DD07200EA676@yugabyte.com> <20221118221305.ku2ibj2bowahzn2y@hjp.at> <11d24370-18c6-f736-85db-e9ae1814bb64@gmail.com> <20221119085225.uivmxue2gef5utv2@hjp.at> <40623F5C-5B99-4AFD-9AA6-ABFFE6B17606@yugabyte.com> <6f5bb172-eea8-3456-60ab-0dd332b89d56@aklaver.com> <4380c01d-a182-8c13-f4e2-278ba8a3cf01@aklaver.com> <9B82247D-3F56-47C1-A918-18E2E8DEDFAB@yugabyte.com> <487898A1-46F5-4351-9BEA-D7170BDBC9D5@yugabyte.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: <487898A1-46F5-4351-9BEA-D7170BDBC9D5@yugabyte.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/21/22 11:46, Bryn Llewellyn wrote: >>> >>> Nobody supports it! >> >> I went back through the thread and don't anywhere when you made the >> above statement, correct me if I am wrong. In that case there was >> nothing to support or not support until now. What people where >> responding to the title of the thread: >> >>> "Seeking practice recommendation: is there ever a use case to have >>> two or more superusers?" >> >> That is a different ask. > > I didn't mean to say that I'd already written the sentence that starts > "It is good practice to limit the number of superuser roles that exist > in a cluster...". Sorry if I gave that impression. It was just a > strawman version of what I practice recommendation might look like that > used the same general wording style as the one about "a role that has > the CREATEDB and CREATEROLE". > Still, why the "Nobody supports it!" statement for a recommendation that only appeared at the same time? I for one have a poor record of mind reading and/or predicting the future:) -- Adrian Klaver adrian.klaver@aklaver.com