Content-Type: multipart/alternative;
 boundary="------------FW32xsiWuJjGCX2T0JlbWoxd"
Message-ID: <302fc72f-fe11-4ea3-b6a8-80bb3ae4359f@gmail.com>
Date: Wed, 25 Oct 2023 15:39:29 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: User/Roles, Owner, and privileges migration strategy
Content-Language: en-US
To: pgsql-admin@lists.postgresql.org
References: <202310251932.ozy6lrpoinh2@alvherre.pgsql>
From: Ron <ronljohnsonjr@gmail.com>
In-Reply-To: <202310251932.ozy6lrpoinh2@alvherre.pgsql>
Archived-At: 
 <https://www.postgresql.org/message-id/302fc72f-fe11-4ea3-b6a8-80bb3ae4359f%40gmail.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------FW32xsiWuJjGCX2T0JlbWoxd
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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.
--------------FW32xsiWuJjGCX2T0JlbWoxd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    On 10/25/23 14:32, Alvaro Herrera wrote:<br>
    <blockquote type="cite"
      cite="mid:202310251932.ozy6lrpoinh2@alvherre.pgsql">
      <pre class="moz-quote-pre" wrap="">On 2023-Oct-25, Tom Lane wrote:

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">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.
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
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.
</pre>
    </blockquote>
    <span style="white-space: pre-wrap">
You can definitely run CREATE ROLE, ALTER ROLE and GRANT statements in AWS RDS Postgresql.  You're just not going to get password hashes.

</span><br>
    <div class="moz-signature">-- <br>
      Born in Arizona, moved to Babylonia.</div>
  </body>
</html>

--------------FW32xsiWuJjGCX2T0JlbWoxd--