public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: PG-General Mailing List <[email protected]>
Subject: Re: question on plain pg_dump file usage
Date: Tue, 17 Sep 2024 08:43:36 -0400
Message-ID: <CANzqJaAbLqut5+Kq5Crc=g4FJjgi7FFLqgAvAOCAgdx06RNHdg@mail.gmail.com> (raw)
In-Reply-To: <GV0P278MB009945F8EA0D8D6B2CF9D91D8B612@GV0P278MB0099.CHEP278.PROD.OUTLOOK.COM>
References: <GV0P278MB009945F8EA0D8D6B2CF9D91D8B612@GV0P278MB0099.CHEP278.PROD.OUTLOOK.COM>
On Tue, Sep 17, 2024 at 8:22 AM Zwettler Markus (OIZ) <
[email protected]> wrote:
> I have to do an out-of-place Postgres migration from PG12 to PG16 using:
>
>
>
> pg_dump -F p -f dump.sql …
>
> sed -i "s/old_name/new_name/g"
>
> psql -f dump.sql …
>
>
>
> Both databases are on UTF-8.
>
>
>
> I wonder if there could be character set conversion errors here, as the
> data is temporarily written to a plain text file.
>
>
Why must it be a plain text dump instead of a custom or directory dump?
Restoring to a new (and differently-named( database is perfectly doable.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> crustacean!
view thread (2+ messages) latest in thread
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: question on plain pg_dump file usage
In-Reply-To: <CANzqJaAbLqut5+Kq5Crc=g4FJjgi7FFLqgAvAOCAgdx06RNHdg@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