From: | Shrikant Bhende <shrikantpostgresql(at)gmail(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_upgrade from 9.5.10 to 12 fails with encoding issue |
Date: | 2020-01-21 05:39:30 |
Message-ID: | CAMTQpJD+uUq1yoYo8Se5kFJAFty0gRvSjJeJXv7AZiY_SkN1XA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Scott,
Thanks for the hint, it worked when I did initdb --locale without
specifying the encoding.
On Mon, Jan 20, 2020 at 11:07 AM Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:
> > On Jan 19, 2020, at 10:00 PM, Shrikant Bhende <
> shrikantpostgresql(at)gmail(dot)com> wrote:
> >
> > Hello community,
> >
> > I am trying to upgrade a cluster of version 9.5.19 to version 12.1 but
> seems like upgrade is getting failed because of database encoding issue, I
> am getting below error while running pg_upgrade command with -c
> >
> > "lc_collate values for database "postgres" do not match: old
> "en_US.UTF-8", new "C.UTF-8" Failure, exiting",
> >
> > I have tried to create new cluster f version 12 using initdb --encoding
> parameter but it create encoding as C.UTF-8 only and old cluster is with
> encoding en_us_UTF-8.
> > Kindly assist to resolve this issue.
> >
> > Thanks and regards
>
> I'm going to guess that you need --locale as well.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Shrikant Bhende | 2020-01-21 09:30:24 | pg_upgrade from 9.5 to 12 fails due to plpythonu2 |
Previous Message | Tom Lane | 2020-01-20 15:59:03 | Re: Restore fails if using multiple threads and database is dumped through pipe |