pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_upgrade from 9.5.10 to 12 fails with encoding issue
3+ messages / 2 participants
[nested] [flat]
* pg_upgrade from 9.5.10 to 12 fails with encoding issue
@ 2020-01-20 05:00 Shrikant Bhende <shrikantpostgresql@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Shrikant Bhende @ 2020-01-20 05:00 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org; pgsql-admin
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: pg_upgrade from 9.5.10 to 12 fails with encoding issue
@ 2020-01-20 05:37 Scott Ribe <scott_ribe@elevated-dev.com>
parent: Shrikant Bhende <shrikantpostgresql@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Scott Ribe @ 2020-01-20 05:37 UTC (permalink / raw)
To: Shrikant Bhende <shrikantpostgresql@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org; pgsql-admin
> On Jan 19, 2020, at 10:00 PM, Shrikant Bhende <shrikantpostgresql@gmail.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.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: pg_upgrade from 9.5.10 to 12 fails with encoding issue
@ 2020-01-21 05:39 Shrikant Bhende <shrikantpostgresql@gmail.com>
parent: Scott Ribe <scott_ribe@elevated-dev.com>
0 siblings, 0 replies; 3+ messages in thread
From: Shrikant Bhende @ 2020-01-21 05:39 UTC (permalink / raw)
To: Scott Ribe <scott_ribe@elevated-dev.com>; +Cc: pgsql-admin@lists.postgresql.org; 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@elevated-dev.com>
wrote:
> > On Jan 19, 2020, at 10:00 PM, Shrikant Bhende <
> shrikantpostgresql@gmail.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.
>
>
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2020-01-21 05:39 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-01-20 05:00 pg_upgrade from 9.5.10 to 12 fails with encoding issue Shrikant Bhende <shrikantpostgresql@gmail.com>
2020-01-20 05:37 ` Scott Ribe <scott_ribe@elevated-dev.com>
2020-01-21 05:39 ` Shrikant Bhende <shrikantpostgresql@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox