Feedback-ID: ia2694551:Fastmail
Date: Wed, 25 Oct 2023 21:32:08 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Aditya D <dsaditya91@gmail.com>, Ron <ronljohnsonjr@gmail.com>,
	pgsql-admin@lists.postgresql.org
Subject: Re: User/Roles, Owner, and privileges migration strategy
Message-ID: <202310251932.ozy6lrpoinh2@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1004361.1698256270@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/202310251932.ozy6lrpoinh2%40alvherre.pgsql>
Precedence: bulk

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.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/