From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | jan(dot)heckman(at)gmail(dot)com |
Subject: | UTF8 conversion |
Date: | 2020-07-25 09:41:59 |
Message-ID: | 159567011970.625.15282665367468168691@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-07-25 15:06:17 | Re: UTF8 conversion |
Previous Message | Peter Geoghegan | 2020-07-24 19:55:01 | Re: Default setting for enable_hashagg_disk |
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2020-07-25 12:04:12 | Re: is JIT available |
Previous Message | David Rowley | 2020-07-25 06:58:39 | Re: bad JIT decision |