pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: MichaelDBA <MichaelDBA@sqlexec.com>
To: Wells Oliver <wells.oliver@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Migrating local PG instance to AWS RDS?
Date: Thu, 27 May 2021 18:56:25 -0400
Message-ID: <cd79261e-51ae-c719-1ca9-c18066f7e4c4@sqlexec.com> (raw)
In-Reply-To: <CAOC+FBX=6vkFQmwLxeUppetX0SSdLDJs7FPG-KkQ8F92Cz9TAA@mail.gmail.com>
References: <CAOC+FBX=6vkFQmwLxeUppetX0SSdLDJs7FPG-KkQ8F92Cz9TAA@mail.gmail.com>

A few things things come to mind...

1. Check what extensions you are using locally and see if they are 
supported in RDS and implement a work-around if possible.

2. Access control in RDS is a bit different considering how AWS 
implements the superuser.  It is really a subset of a superuser, hence, 
called rds_superuser.  The problem with that is that if you have 
multiple rds_superusers creating objects then be ready to deal with the 
situation that rds_superusers cannot control objects created by other 
rds_superusers.  You can get around these things awkwardly with REASSIGN 
and DROP OWNED BY.

3. Make sure you are not using LOs (Large Objects) for blob data.  Use 
bytea.  Restrictions and performance hits in RDS for using LOs.

4. You are restricted with respect to certain system tables: pg_shadow, 
pg_user (no password access) , pg_roles, pg_authid and more.  Also, you 
cannot get cluster info (roles, etc.) since you are not allowed to 
execute "pg_dumpall -g".

Regards,
Michael Vitale



Wells Oliver wrote on 5/27/2021 5:49 PM:
> Anyone have a handy write-up or useful experience to share in 
> migrating local PG databases to Amazon's RDS?
>
> I was thinking of making a failover in RDS and promoting it after 
> replication or something to that effect, but I thought I would see if 
> there's some more canonical approach.
>
> Thanks.
>
> -- 
> Wells Oliver
> wells.oliver@gmail.com <mailto:wellsoliver@gmail.com>

view thread (9+ messages)  latest in thread

Message-ID: <cd79261e-51ae-c719-1ca9-c18066f7e4c4@sqlexec.com>
Permalink:  ../cd79261e-51ae-c719-1ca9-c18066f7e4c4@sqlexec.com/
Also on:    postgresql.org/message-id/cd79261e-51ae-c719-1ca9-c18066f7e4c4@sqlexec.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: MichaelDBA@sqlexec.com, wells.oliver@gmail.com
  Subject: Re: Migrating local PG instance to AWS RDS?
  In-Reply-To: <cd79261e-51ae-c719-1ca9-c18066f7e4c4@sqlexec.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox