| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fwd: PQexecPrepared() question |
| Date: | 2025-12-19 21:21:11 |
| Message-ID: | 952d0035-237c-415e-8505-24939821cd56@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/19/25 11:12, Ron Johnson wrote:
> On Fri, Dec 19, 2025 at 1:52 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
> <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
>
> Igor Korot <ikorot01(at)gmail(dot)com <mailto:ikorot01(at)gmail(dot)com>> writes:
> > But what is the purpose of setting client encoding on the server?
> It is for
> > the client
>
> No, it's to tell the server what encoding to transmit to the client
> (as well as what encoding strings coming from the client are in).
>
>
> If there's an encoding mismatch between the server and client, does
> "something" (like a PQ driver) convert text in the data stream from the
> source encoding to the target encoding?
It is explained here:
https://www.postgresql.org/docs/current/multibyte.html#MULTIBYTE-AUTOMATIC-CONVERSION
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Korot | 2025-12-20 04:10:12 | Re: PQexecPrepared() question |
| Previous Message | Tom Lane | 2025-12-19 19:18:15 | Re: Fwd: PQexecPrepared() question |