| From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, Srinath Reddy <srinath2133(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Non-text mode for pg_dumpall |
| Date: | 2025-03-11 23:14:30 |
| Message-ID: | CAMsGm5eRZqxJq7UYL9vY7vZ4F+kSR3vb9D4FPdqeTPTP0PJmYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 11 Mar 2025 at 18:37, Andrew Dunstan <andrew(at)dunslane(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2025-03-11 23:26:15 | Re: pg_rewind with --write-recovery-conf option doesn't write dbname to primary_conninfo value. |
| Previous Message | Peter Geoghegan | 2025-03-11 22:59:09 | Re: Adding skip scan (including MDAM style range skip scan) to nbtree |