From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Postgres limitation in user management
Date: Sat, 4 Nov 2023 09:45:01 -0500
Message-ID: <1cda5011-4de0-4a85-bebb-79d0cbe7a12f@gmail.com> (raw)
In-Reply-To: <SJ0PR03MB6304FF2873FD903C710CE8C283A5A@SJ0PR03MB6304.namprd03.prod.outlook.com>
References: <SJ0PR03MB6304FF2873FD903C710CE8C283A5A@SJ0PR03MB6304.namprd03.prod.outlook.com>
How can you /practically/ support a database without being able to look at a
table?
On 11/3/23 01:26, Kar, Swapnil (TR Technology) wrote:
>
> Hello Team,
>
> I am facing a limitation with Postgres user management and require your
> assistance or input around it. Let me brief you the scenario here –
>
> We have 2 sets of database user groups –
>
> 1. *App*– who owns the application schemas (and tables)
> 2. *Support*– who provides db support
>
> We want Support users to have no SELECT or DML privilege but only ALTER
> TABLE to perform any troubleshooting in the database.
>
> In Postgres, to have alter system privilege one should be the owner of the
> schema/table but App users are not keen to make them temporarily as owner
> of the schema during the investigation time. Because they loose the
> ownership and can’t perform ALTER table commands.
>
> Now another option 2 is to – grant app_user to support_user;
>
> This way ownership is not transferred but support is able to perform
> select and DML.
>
> Option 3 is to grant rds_superuser privilege to support and in this case
> they will become more powerful superuser in the DB. This is also not a
> solution for our requirement.
>
> Do you think there is a way to deal with this situation ?
>
> Any help and guidance here is highly appreciated.
>
> Regards,
>
> Swapnil
>
> This e-mail is for the sole use of the intended recipient and contains
> information that may be privileged and/or confidential. If you are not an
> intended recipient, please notify the sender by return e-mail and delete
> this e-mail and any attachments. Certain required legal entity disclosures
> can be accessed on our website:
> https://www.thomsonreuters.com/en/resources/disclosures.html
--
Born in Arizona, moved to Babylonia.
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: ronljohnsonjr@gmail.com
Subject: Re: Postgres limitation in user management
In-Reply-To: <1cda5011-4de0-4a85-bebb-79d0cbe7a12f@gmail.com>
References: <SJ0PR03MB6304FF2873FD903C710CE8C283A5A@SJ0PR03MB6304.namprd03.prod.outlook.com> <1cda5011-4de0-4a85-bebb-79d0cbe7a12f@gmail.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