| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Aditya D <dsaditya91(at)gmail(dot)com>, Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: User/Roles, Owner, and privileges migration strategy |
| Date: | 2023-10-25 19:32:08 |
| Message-ID: | 202310251932.ozy6lrpoinh2@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2023-10-25 20:39:29 | Re: User/Roles, Owner, and privileges migration strategy |
| Previous Message | Tom Lane | 2023-10-25 17:51:10 | Re: User/Roles, Owner, and privileges migration strategy |