From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: User/Roles, Owner, and privileges migration strategy
Date: Wed, 25 Oct 2023 15:39:29 -0500
Message-ID: <302fc72f-fe11-4ea3-b6a8-80bb3ae4359f@gmail.com> (raw)
In-Reply-To: <202310251932.ozy6lrpoinh2@alvherre.pgsql>
References: <202310251932.ozy6lrpoinh2@alvherre.pgsql>
On 10/25/23 14:32, Alvaro Herrera wrote:
> On 2023-Oct-25, Tom Lane wrote:
>
>> I kind of suspect that that's going to be a dead end. If you can't
>> run dump and restore as superuser, it's going to be very hard to deal
>> with a multi-user database, unless you use --no-owner which of course
>> doesn't restore the multiple object ownerships.
>>
>> You might have to resort to separately dumping the objects belonging
>> to each user, and then running each restore as that user.
> In Postgres you're probably right, but I understood that this is RDS,
> which offers a superuser-of-sorts. It allows some alien stuff to be
> done. Though ... re-reading the question, I see now he's saying it may
> be RDS or maybe *other* DBaaS providers, so maybe it works and maybe it
> doesn't, depending on the specifics.
You can definitely run CREATE ROLE, ALTER ROLE and GRANT statements in AWS
RDS Postgresql. You're just not going to get password hashes.
--
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: User/Roles, Owner, and privileges migration strategy
In-Reply-To: <302fc72f-fe11-4ea3-b6a8-80bb3ae4359f@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