From: | "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch> |
---|---|
To: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | WG: question on plain pg_dump file usage |
Date: | 2024-09-17 13:27:42 |
Message-ID: | GV0P278MB00996F003F2A695EFAF823948B612@GV0P278MB0099.CHEP278.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Von: Zwettler Markus (OIZ) <Markus(dot)Zwettler(at)zuerich(dot)ch>
Gesendet: Dienstag, 17. September 2024 14:22
An: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Betreff: question on plain pg_dump file usage
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.
Thanks, Markus
I found that the tempory plain text file is also encoded in UTF-8.
There should not be any problem so. Agreed?
$ file -bi dump.sql
text/plain; charset=utf-8
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-09-17 14:02:34 | Re: question on plain pg_dump file usage |
Previous Message | Greg Sabino Mullane | 2024-09-17 13:18:02 | Re: question on plain pg_dump file usage |