| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| 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 17:51:10 |
| Message-ID: | 1004361.1698256270@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2023-Oct-24, Aditya D wrote:
>> Thanks a lot Holger and Ron for the reply and valuable inputs. AWS RDS or
>> any other PaaS PostgreSQL instances does not support Superuser and to avoid
>> multiple pg_dump statements from on-premises to PaaS, is there any
>> recommended way?
> I would do this using the following steps:
> ...
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2023-10-25 19:32:08 | Re: User/Roles, Owner, and privileges migration strategy |
| Previous Message | Gambhir Singh | 2023-10-25 15:00:22 | Predefined Role - pg_write_all_data |