Message-ID: <06681f6909b0602f731bb69409f17ad912795f86.camel@cybertec.at>
Subject: Re: Non-text mode for pg_dumpall
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Isaac Morland <isaac.morland@gmail.com>, Andrew Dunstan
	 <andrew@dunslane.net>
Cc: =?ISO-8859-1?Q?=C1lvaro?= Herrera <alvherre@alvh.no-ip.org>, Dagfinn
 Ilmari =?ISO-8859-1?Q?Manns=E5ker?=
	 <ilmari@ilmari.org>, Mahendra Singh Thalor <mahi6run@gmail.com>, jian he
	 <jian.universality@gmail.com>, Srinath Reddy <srinath2133@gmail.com>,
	pgsql-hackers@lists.postgresql.org
Date: Wed, 12 Mar 2025 08:24:27 +0100
In-Reply-To: 
 <CAMsGm5eRZqxJq7UYL9vY7vZ4F+kSR3vb9D4FPdqeTPTP0PJmYQ@mail.gmail.com>
References: <202503112103.fltgs54vpq6f@alvherre.pgsql>
	 <a84a3e28-7517-4e5c-8049-395816278c81@dunslane.net>
	 <CAMsGm5eRZqxJq7UYL9vY7vZ4F+kSR3vb9D4FPdqeTPTP0PJmYQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/06681f6909b0602f731bb69409f17ad912795f86.camel%40cybertec.at>
Precedence: bulk

On Tue, 2025-03-11 at 19:14 -0400, Isaac Morland wrote:
> On Tue, 11 Mar 2025 at 18:37, Andrew Dunstan <andrew@dunslane.net> wrote:
>=20
> > Well, JSON is supposed to be UTF8. What should we do about database=20
> > names that are not UTF8?
>=20
> How can you have a database name that isn't encodeable in UTF-8? At this =
point
> I'm pretty sure Unicode has subsumed essentially every character ever men=
tioned
> in a standards document.

There is a difference between "encodable" and "encoded".  You'd have to fig=
ure
out the actual encoding of the database name and convert that to UTF-8.

Yours,
Laurenz Albe