From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | jan(dot)heckman(at)gmail(dot)com |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: UTF8 conversion |
Date: | 2020-07-25 15:06:17 |
Message-ID: | 673790.1595689577@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
PG Doc comments form <noreply(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2020-07-25 16:38:03 | Re: Default setting for enable_hashagg_disk |
Previous Message | PG Doc comments form | 2020-07-25 09:41:59 | UTF8 conversion |
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2020-07-25 15:24:26 | Re: TDE implementation in postgres which is in docker container |
Previous Message | Tom Lane | 2020-07-25 14:54:18 | Re: bad JIT decision |