Re: database encoding migration from a pg_dumpall set - Mailing list pgsql-novice

From Steve T
Subject Re: database encoding migration from a pg_dumpall set
Date
Msg-id 8b9985e6e88e9f9519d6e415c9d6408116668c6b.camel@yahoo.co.uk
Whole thread Raw
In response to Re: database encoding migration from a pg_dumpall set  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-novice
On Sat, 2022-08-13 at 11:33 -0400, Tom Lane wrote:
> 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).

Thanks Tom.
I did try doing another dumpall with the encoding set on that - but no joy.
I'll edit the dumpall if that's a legit way.

Thanks again.
Steve



pgsql-novice by date:

Previous
From: Tom Lane
Date:
Subject: Re: database encoding migration from a pg_dumpall set
Next
From: awolchute@tutanota.com
Date:
Subject: How to use a cross column exclude constraint