Message-ID: <5ef09c253188681e2beeb975d96d7ebf861f2b10.camel@cybertec.at>
Subject: Re: PQexecPrepared() question
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Igor Korot <ikorot01@gmail.com>
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: Sat, 20 Dec 2025 18:02:13 +0100
In-Reply-To: <CA+FnnTxOzSBj-YZmsCcQ-2khU4pG=O1C5qdX8huyTwvRXHA9qg@mail.gmail.com>
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+FnnTyYBNwbzFs5GqO+SMg3g60jPTsnmFwTV=_s_YboGo-68A@mail.gmail.com>
	 <852dee881b6cc82b9d4b51d69d48c415e2a87b4d.camel@cybertec.at>
	 <CA+FnnTxOzSBj-YZmsCcQ-2khU4pG=O1C5qdX8huyTwvRXHA9qg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-2.fc42) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/5ef09c253188681e2beeb975d96d7ebf861f2b10.camel%40cybertec.at>
Precedence: bulk

On Fri, 2025-12-19 at 23:04 -0800, Igor Korot wrote:
> > SQL_ASCII as client encoding means that no conversion will take place.
> >=20
> > Still, the database encoding (I suspect UTF8) will govern what can be s=
tored
> > in the database.=C2=A0 Anything that is not valid UTF-8 will be rejecte=
d.
>=20
> Rejected how?

As you experienced: by throwing an error.

> > A SELECT will never cause an error - the client will just receive data
> > in UTF-8.
>=20
> And then what?

The *client application* will receive UTF-8 data.

Yours,
Laurenz Albe