Re: Non-text mode for pg_dumpall - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: Non-text mode for pg_dumpall
Date
Msg-id 06681f6909b0602f731bb69409f17ad912795f86.camel@cybertec.at
Whole thread Raw
In response to Re: Non-text mode for pg_dumpall  (Isaac Morland <isaac.morland@gmail.com>)
List pgsql-hackers
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:
>
> > Well, JSON is supposed to be UTF8. What should we do about database
> > names that are not UTF8?
>
> 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 mentioned
> in a standards document.

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

Yours,
Laurenz Albe



pgsql-hackers by date:

Previous
From: newtglobal postgresql_contributors
Date:
Subject: Re: [PoC] Reducing planning time when tables have many partitions
Next
From: Xuneng Zhou
Date:
Subject: Re: Proposal: Limitations of palloc inside checkpointer