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

From Isaac Morland
Subject Re: Non-text mode for pg_dumpall
Date
Msg-id CAMsGm5eRZqxJq7UYL9vY7vZ4F+kSR3vb9D4FPdqeTPTP0PJmYQ@mail.gmail.com
Whole thread Raw
In response to Re: Non-text mode for pg_dumpall  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Non-text mode for pg_dumpall
List pgsql-hackers
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.

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Adding skip scan (including MDAM style range skip scan) to nbtree
Next
From: Masahiko Sawada
Date:
Subject: Re: pg_rewind with --write-recovery-conf option doesn't write dbname to primary_conninfo value.