From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: jan.heckman@gmail.com
Subject: UTF8 conversion
Date: Sat, 25 Jul 2020 09:41:59 +0000
Message-ID: <159567011970.625.15282665367468168691@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/functions-string.html
Description:
I cannot get psql to accept an UTF8 string, link update .. set ... =
'josé';
In the docpage on encodings, jose is used in examples for UTF8.
Plainly this makes no sense. If you give examples, use the specifics in
question, like a proper UTF8 string such as 'josé'.
That would help me, and probably quite a few others, greatly.
I can go in a song and dance about my settings. Believe me, I a proper
client_encoding and database encoding, and done umpteen attempts, but using
UTF8 in psql queries (without UGLY \u notation) appears completely
impossible.
Example: select 'jose'; Works fine. select 'josé'; will just hang, even if
embellished with ::utf8 or ::bytea.
When executing the query, psql does not return to its prompt until using ^c.
One might believe it is executing the query, but that simply is not so.
Then it shows it has not found the end of the string.
This mis-behavior irritates me wildly in an otherwise great product.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, jan.heckman@gmail.com
Subject: Re: UTF8 conversion
In-Reply-To: <159567011970.625.15282665367468168691@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox