From: Tony Bazeley <tonyb@tonyb.id.au>
To: pgsql-general@lists.postgresql.org
Subject: Re: pg_dumpall - restoration problem- resolved
Date: Sun, 07 Apr 2024 22:48:43 +0930
Message-ID: <2519686.gUQCWdUFS2@apn53>
In-Reply-To: <2634671.1712451944@sss.pgh.pa.us>
References: <3625230.PrqTZ78sOi@apn53> <2634671.1712451944@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Archived-At: 
 <https://www.postgresql.org/message-id/2519686.gUQCWdUFS2%40apn53>
Precedence: bulk

Thanks Tom,

Dumped in Ubuntu 22.04_1 and restore attempted using Ubuntu 22.04.3
Editing the dump file to C.UTF8 didn't solve the problem.

The default for the database was en_AU.utf8 so I should have changed the=20
collation to that, but it was one field in one table of superseded data, so=
 I=20
just erased the collation from that field. =20

Still no idea on how it came to be there.

Cheers
Tony


On Sunday 7 April 2024 10:35:44=E2=80=AFAM ACST Tom Lane wrote:
> Tony Bazeley <tonyb@tonyb.id.au> writes:
> > I've a problem with restoring a cluster created with pg_dump_all from 1=
4.8
> > ( pg_dumpall >pgall.out and then psql -f pgall.out postgres).
> > ...
> > Attempting to restore to postgresql-16 results in errors
> >=20
> > 2024-04-05 22:17:15.418 ACDT [6565] postgres@tonbaz ERROR:  collation
> > "pg_catalog.C.UTF-8" for encoding "UTF8" does not exist at character 366
> >=20
> > I don't understand the class text COLLATE pg_catalog."C.UTF-8"  syntax,
> > but
> > select * from pg_collation shows a C.UTF8 but no C.UTF-8
>=20
> I take it you are trying to restore onto a different OS platform with
> different locale naming conventions.  The easiest way to deal with it
> probably is to edit the dump file and change "C.UTF-8" to "C.UTF8"
> everywhere.  (Manually editing an 8G dump file might be no fun, but
> "sed" should make short work of it.)
>=20
> 			regards, tom lane