Re: database encoding migration from a pg_dumpall set

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: stevetucknott(at)yahoo(dot)co(dot)uk
Cc: PostGreSQL <pgsql-novice(at)postgresql(dot)org>
Subject: Re: database encoding migration from a pg_dumpall set
Date: 2022-08-13 15:33:47
Message-ID: 287927.1660404827@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Steve T <stevetucknott(at)yahoo(dot)co(dot)uk> writes:
> Is there an official way for migrating database encodings?

Not via pg_dumpall. If you dump the databases individually,
then you can create them manually on the target installation
with whatever encoding (or other properties) you want,
finishing by restoring the per-DB dumps into the respective
new databases.

Another way is to manually edit the pg_dumpall output
script and change the encoding options in the CREATE
DATABASE commands (but NOT the "SET client_encoding"
commands).

regards, tom lane

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Steve T 2022-08-14 06:17:25 Re: database encoding migration from a pg_dumpall set
Previous Message Steve T 2022-08-13 15:10:10 database encoding migration from a pg_dumpall set