pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter J. Holzer <hjp-pgsql@hjp.at>
To: pgsql-general@lists.postgresql.org
Subject: Re: Seeking practice recommendation: is there ever a use case to have two or more superusers?
Date: Sat, 19 Nov 2022 09:52:25 +0100
Message-ID: <20221119085225.uivmxue2gef5utv2@hjp.at> (raw)
In-Reply-To: <11d24370-18c6-f736-85db-e9ae1814bb64@gmail.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>

On 2022-11-18 16:21:18 -0600, Ron wrote:
> On 11/18/22 16:13, Peter J. Holzer wrote:
> > So you can give these credentials to you developers or devops folks
> > (whom you trust not attack the system -
> 
> They like to "fix" things without documenting what they did, and then, when
> something breaks, denying they did anything (or honestly not believing that
> whatever "trivial" thing they did could any major or deliterious impact).

Which is why you want to automate deployments. When the easiest way to
fix something in production is to just push the change into the repo,
this is what people will do. When doing it the "proper" way is much more
complicated than just fudging it, people will do the latter.

        hp

-- 
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (20+ messages)  latest in thread

Message-ID: <20221119085225.uivmxue2gef5utv2@hjp.at>
Permalink:  ../20221119085225.uivmxue2gef5utv2@hjp.at/
Also on:    postgresql.org/message-id/20221119085225.uivmxue2gef5utv2@hjp.at

 · 

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: hjp-pgsql@hjp.at
  Subject: Re: Seeking practice recommendation: is there ever a use case to have two or more superusers?
  In-Reply-To: <20221119085225.uivmxue2gef5utv2@hjp.at>
  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>

* 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