From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: pg_restore but for full user and roles, etc |
Date: | 2024-07-26 17:15:32 |
Message-ID: | CAOC+FBVbUJn=UJRsAS4nUhnOjmFOCRDNcuN-cEZVOT4X3v+wtQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks. Yeah, I was basically looking for the role/user only version of
pg_dumpall -g, where I'd then handle specific DB restore on its own. Your
right thought, I can copy out what I care about from the output.
On Fri, Jul 26, 2024 at 10:06 AM Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
wrote:
> On Fri, Jul 26, 2024 at 12:43 PM Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
> wrote:
>
>> I am doing a pg_restore of a database, which is nothing difficult, but I
>> also am creating a new server first, and rather than painstakingly making
>> sure I create all users and roles etc prior to pg_restore (so we can have
>> the same perms), is there some obvious way of doing this I'm unawares of?
>>
>
> Running "pg_dumpall -g > source_roles.sql" and then scanning it for the
> relevant entries doesn't seem too onerous. It's a lot easier than the
> conceptually similar -- but much trickier -- process you need to go through
> when migrating SQL Server databases.
>
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Wells Oliver | 2024-07-26 17:19:11 | Re: pg_restore but for full user and roles, etc |
Previous Message | Ron Johnson | 2024-07-26 17:06:11 | Re: pg_restore but for full user and roles, etc |