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+FnnTyYBNwbzFs5GqO+SMg3g60jPTsnmFwTV=_s_YboGo-68A@mail.gmail.com> <852dee881b6cc82b9d4b51d69d48c415e2a87b4d.camel@cybertec.at>
In-Reply-To: <852dee881b6cc82b9d4b51d69d48c415e2a87b4d.camel@cybertec.at>
From: Igor Korot <ikorot01@gmail.com>
Date: Sat, 20 Dec 2025 21:33:23 -0800
Message-ID: <CA+FnnTwtd-YJo5zp3obQer3qfbacg5s-4b3+5PvUkL3e+5Eh4Q@mail.gmail.com>
Subject: Re: PQexecPrepared() question
To: Laurenz Albe <laurenz.albe@cybertec.at>, 
	"pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BFnnTwtd-YJo5zp3obQer3qfbacg5s-4b3%2B5PvUkL3e%2B5Eh4Q%40mail.gmail.com>
Precedence: bulk

Hi, Laurenz,

On Fri, Dec 19, 2025 at 10:24=E2=80=AFPM Laurenz Albe <laurenz.albe@cyberte=
c.at> wrote:
>
> On Fri, 2025-12-19 at 20:10 -0800, Igor Korot wrote:
> > > > > What is =E2=80=9Cclientencoding in this case?
> > > >
> > > > - if PGCLIENTENCODING is set in the environment of the client execu=
table, that
> > >
> > > No it is not.
> > >
> > > > - otherwise, if "client_encoding" is set on the server, that
> >
> > I just checked the postgres.conf.
> >
> > This file does not have any client_encoding.
> >
> > > > - otherwise, SQL_ASCII
> >
> > Which means that this is an encoding that will be used.
>
> You can verify that with the SQL statement "SHOW client_encoding"
> in your sample program.

I added the following code in my app:

    res =3D PQexec( m_db, "SHOW client_encoding" );
    auto value =3D PQgetvalue( res, 0, 0 );
    PQclear( res );

and the value of the "value" variable is "UTF8".
>
> > But then I don=E2=80=99t understand anything.
> >
> > The code I posted above worked fine on SELECT, but INSERT failed.
> >
> > If the SQL_ASCII is the encoding used both operations should fail. Or b=
oth succeeds.
> >
> > Could someone explain what happened?
>
> SQL_ASCII as client encoding means that no conversion will take place.
>
> Still, the database encoding (I suspect UTF8) will govern what can be sto=
red
> in the database.  Anything that is not valid UTF-8 will be rejected.
>
> A SELECT will never cause an error - the client will just receive data
> in UTF-8.

The exact error message is:

ERROR: invalid byte sequence for encoding UTF8: 0xdf
CONTEXT: unnamed portal parameter $1

on the INSERT.

Thank you.

>
> Yours,
> Laurenz Albe