public inbox for [email protected]  

help / color / mirror / Atom feed

From: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: best migration solution
Date: Thu, 25 Apr 2024 09:14:08 -0400
Message-ID: <CANzqJaD5JG0DQt0OQkF610DSZQwXh+TGceua+MPq3M1=Jdgp0w@mail.gmail.com> (raw)
In-Reply-To: <GV0P278MB0099D9368CEBEBF304405F778B172@GV0P278MB0099.CHEP278.PROD.OUTLOOK.COM>
References: <GV0P278MB0099D9368CEBEBF304405F778B172@GV0P278MB0099.CHEP278.PROD.OUTLOOK.COM>

On Thu, Apr 25, 2024 at 3:55 AM Zwettler Markus (OIZ) <
[email protected]> wrote:

> we have to migrate from hosted PG12 to containerized PG16 on private
> cloud.
>
>
>
> some of the installed PG12 extensions are not offered on the containerized
> PG16, eg. PostGIS related extensions like pg_routing and ogr_fdw.
>
> some of these extensions are not needed anymore. some of these extensions
> were installed in their own schema.
>
> we also need to change the database names and most role names due to
> external requirements.
>
>
>
>
>
> I came up with this solution.
>
>
>
> dump all roles with pg_dumpall.
>
> edit this dumpfile and
>
>    - exclude roles not needed
>    - change required role names
>
>
>
> dump all required databases with pg_dump
>
>    - in plain text
>    - exclude all schemas not needed
>
> edit this dump file and
>
>    - exclude any "create extension" command for not existing extensions
>    - change all required role names on permissions and ownerships
>
>
>
>
>
> any missings?
> any better solutions?
>

How big of a database?

Editing a giant SQL file in vim is painful.

I'd do this, which is conceptually similar to your plan:
* pg_dump -Fd
* pg_restore --list
* Edit the generated list
* pg_restore --use-list=edited_list

 I wonder whether a plain text dump could lead to conversion problems or
> something similar?
>

Maybe, if the collations are different between the source and destination.

view thread (2+ messages)

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: [email protected]
  Cc: [email protected]
  Subject: Re: best migration solution
  In-Reply-To: <CANzqJaD5JG0DQt0OQkF610DSZQwXh+TGceua+MPq3M1=Jdgp0w@mail.gmail.com>

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

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