Re: database encoding migration from a pg_dumpall set

From: Steve T <stevetucknott(at)yahoo(dot)co(dot)uk>
To: pgsql-novice(at)lists(dot)postgresql(dot)org
Subject: Re: database encoding migration from a pg_dumpall set
Date: 2022-08-14 06:17:25
Message-ID: 8b9985e6e88e9f9519d6e415c9d6408116668c6b.camel@yahoo.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message awolchute 2022-08-21 19:45:17 How to use a cross column exclude constraint
Previous Message Tom Lane 2022-08-13 15:33:47 Re: database encoding migration from a pg_dumpall set