WG: [Extern] Re: question on plain pg_dump file usage

From: "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: WG: [Extern] Re: question on plain pg_dump file usage
Date: 2024-09-17 13:16:06
Message-ID: GV0P278MB0099317B453F251ED5E586658B612@GV0P278MB0099.CHEP278.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Von: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Gesendet: Dienstag, 17. September 2024 14:44
An: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Betreff: [Extern] Re: question on plain pg_dump file usage

On Tue, Sep 17, 2024 at 8:22 AM Zwettler Markus (OIZ) <Markus(dot)Zwettler(at)zuerich(dot)ch<mailto:Markus(dot)Zwettler(at)zuerich(dot)ch>> 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!

--- Externe Email: Vorsicht mit Anhängen, Links oder dem Preisgeben von Informationen ---

Because I can simply change the application from the old to the new structure then.

-Regards, Markus

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Sabino Mullane 2024-09-17 13:18:02 Re: question on plain pg_dump file usage
Previous Message Greg Sabino Mullane 2024-09-17 13:13:12 Re: IO related waits