pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Bryn Llewellyn <bryn@yugabyte.com>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: pgsql-general list <pgsql-general@lists.postgresql.org>
Subject: Re: Seeking practice recommendation: is there ever a use case to have two or more superusers?
Date: Mon, 21 Nov 2022 13:36:33 -0800
Message-ID: <db7dc42f-e91b-e7f6-f2e2-eddb58d200e9@aklaver.com> (raw)
In-Reply-To: <487898A1-46F5-4351-9BEA-D7170BDBC9D5@yugabyte.com>
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>
	<Y3tQE9zy4IZU5KEZ@hermes.hilbert.loc>
	<4380c01d-a182-8c13-f4e2-278ba8a3cf01@aklaver.com>
	<9B82247D-3F56-47C1-A918-18E2E8DEDFAB@yugabyte.com>
	<d51cebb0-d12a-7238-bad8-d31bdc60e84e@aklaver.com>
	<487898A1-46F5-4351-9BEA-D7170BDBC9D5@yugabyte.com>

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






view thread (20+ messages)  latest in thread

Message-ID: <db7dc42f-e91b-e7f6-f2e2-eddb58d200e9@aklaver.com>
Permalink:  ../db7dc42f-e91b-e7f6-f2e2-eddb58d200e9@aklaver.com/
Also on:    postgresql.org/message-id/db7dc42f-e91b-e7f6-f2e2-eddb58d200e9@aklaver.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: adrian.klaver@aklaver.com, bryn@yugabyte.com, david.g.johnston@gmail.com
  Subject: Re: Seeking practice recommendation: is there ever a use case to have two or more superusers?
  In-Reply-To: <db7dc42f-e91b-e7f6-f2e2-eddb58d200e9@aklaver.com>
  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> <Y3tQE9zy4IZU5KEZ@hermes.hilbert.loc> <4380c01d-a182-8c13-f4e2-278ba8a3cf01@aklaver.com> <9B82247D-3F56-47C1-A918-18E2E8DEDFAB@yugabyte.com> <d51cebb0-d12a-7238-bad8-d31bdc60e84e@aklaver.com> <487898A1-46F5-4351-9BEA-D7170BDBC9D5@yugabyte.com> <db7dc42f-e91b-e7f6-f2e2-eddb58d200e9@aklaver.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox