MIME-Version: 1.0
References: <CA+FnnTygjVvSmzTHnvteuL4KEC=0P_+mF8Kn84JtNGZWUGxpUA@mail.gmail.com>
 <2547700.1765940917@sss.pgh.pa.us> <CA+FnnTxO6kam9=mRonvsnUA1OxJxdDdQsj+ubdgFNNb9b3WMPQ@mail.gmail.com>
 <9a0ce31a49f149d8d982d2b359095560655f781e.camel@cybertec.at>
 <CA+FnnTzE34VJWR7xkymaKEwXiiQ8j3o03m0+qcQsRr2JkRQLwQ@mail.gmail.com>
 <ebaca1066dfdf567d158fc48dce86a6fcc132988.camel@cybertec.at>
 <CA+FnnTz5tcJEL12ir1nxe9q75rxaAdfBtcFUNiD4R5gW_JR23A@mail.gmail.com>
 <CA+FnnTwqKJQ-AnDHLzmhYra5QaLfTmEJ9=yw+bxADA0=bp1z8g@mail.gmail.com> <3360047.1766170334@sss.pgh.pa.us>
In-Reply-To: <3360047.1766170334@sss.pgh.pa.us>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Fri, 19 Dec 2025 14:12:37 -0500
Message-ID: <CANzqJaCxGFizjSbSGY=0MEK4WR6aqc62YR5mWT3rBzktG9FRXg@mail.gmail.com>
Subject: Re: Fwd: PQexecPrepared() question
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000f88307064652dce8"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaCxGFizjSbSGY%3D0MEK4WR6aqc62YR5mWT3rBzktG9FRXg%40mail.gmail.com>
Precedence: bulk

--000000000000f88307064652dce8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Dec 19, 2025 at 1:52=E2=80=AFPM Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Igor Korot <ikorot01@gmail.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?

--=20
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

--000000000000f88307064652dce8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Dec 19, 2025 at 1:52=E2=80=AFPM T=
om Lane &lt;<a href=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt; =
wrote:</div><div class=3D"gmail_quote gmail_quote_container"><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex">Igor Korot &lt;<a href=3D"mailto:ikorot=
01@gmail.com" target=3D"_blank">ikorot01@gmail.com</a>&gt; writes:<br>
&gt; But what is the purpose of setting client encoding on the server? It i=
s for<br>
&gt; the client<br>
<br>
No, it&#39;s to tell the server what encoding to transmit to the client<br>
(as well as what encoding strings coming from the client are in).<br></bloc=
kquote><div><br></div><div></div></div><div>If there&#39;s an encoding mism=
atch between the server and client, does &quot;something&quot; (like a PQ d=
river) convert text in the data stream from the source encoding to the targ=
et encoding?</div><div><br></div><span class=3D"gmail_signature_prefix">-- =
</span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Deat=
h to &lt;Redacted&gt;, and butter sauce.<div>Don&#39;t boil me, I&#39;m sti=
ll alive.<br><div><div>&lt;Redacted&gt; lobster!</div></div></div></div></d=
iv></div>

--000000000000f88307064652dce8--