pg.ddx.io pgsql-general@postgresql.org mailing list archivehelp / color / mirror / Atom feed
UTF8 conversion 2+ messages / 2 participants [nested] [flat]
* UTF8 conversion @ 2020-07-25 09:41 PG Doc comments form <noreply@postgresql.org> 0 siblings, 1 reply; 2+ messages in thread From: PG Doc comments form @ 2020-07-25 09:41 UTC (permalink / raw) To: pgsql-docs@lists.postgresql.org; +Cc: jan.heckman@gmail.com 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. ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: UTF8 conversion @ 2020-07-25 15:06 Tom Lane <tgl@sss.pgh.pa.us> parent: PG Doc comments form <noreply@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2020-07-25 15:06 UTC (permalink / raw) To: jan.heckman@gmail.com; +Cc: pgsql-docs@lists.postgresql.org PG Doc comments form <noreply@postgresql.org> writes: > I cannot get psql to accept an UTF8 string, link update .. set ... = > 'josé'; What this sounds like is some confusion in your locale and/or encoding settings. While perhaps we could improve the documentation about that area, it's impossible to guess what would help you, since it's not clear exactly what's wrong. > 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. Without those details it's really impossible to say much. But I'm suspicious that this isn't a Postgres issue at all really, but something not right about your terminal settings and/or locale environment variables. Anyway, a documentation comment box isn't the right place for this kind of support, and I seriously doubt that there's any bug here either. Please send more detail to the pgsql-general mailing list, and we'll see if we can work this out. regards, tom lane ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2020-07-25 15:06 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2020-07-25 09:41 UTF8 conversion PG Doc comments form <noreply@postgresql.org> 2020-07-25 15:06 ` Tom Lane <tgl@sss.pgh.pa.us>
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