MIME-Version: 1.0
References: <20240213193732.28cb8329@slate.karlpinc.com>
 <CA+mi_8Y0jzEZA+3kCnTtWCS8cvWTUFcD=0J+ihiamh=y8GvOxg@mail.gmail.com>
 <20240214094203.52d7e22d@slate.karlpinc.com>
In-Reply-To: <20240214094203.52d7e22d@slate.karlpinc.com>
From: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Date: Wed, 14 Feb 2024 19:28:57 +0100
Message-ID: 
 <CA+mi_8bKxi286PjqYrt9Epcd2dxL+vFtMDJuyurV2edsOEMqJg@mail.gmail.com>
Subject: Re: Reporting UnicodeEncodeError info on arbitrary data sent to PG
 with psycopg3
To: "Karl O. Pinc" <kop@karlpinc.com>
Cc: "psycopg@postgresql.org" <psycopg@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2Bmi_8bKxi286PjqYrt9Epcd2dxL%2BvFtMDJuyurV2edsOEMqJg%40mail.gmail.com>
Precedence: bulk

Hello,

On Wed, 14 Feb 2024 at 16:42, Karl O. Pinc <kop@karlpinc.com> wrote:

> I did not use conn.info.encoding because the docs say that it
> contains the _client_ encoding, not the server-side encoding
> used to store the db content.
> [...]
> Confirming the encodings, connecting to the  "latin1" db with psql shows:

> kop_latin1=> show client_encoding;
>  UTF8
>
> kop_latin1=> show server_encoding;
>  LATIN1
>
> But, conn.info.encoding does return iso8859-1.
>
> So I think your documentation has confused client
> and server in this case.  If you can confirm this
> for me I'll go ahead and use conn.info.encoding.

No, I am pretty sure that this is the client encoding that is
reported. It comes from here:

https://github.com/psycopg/psycopg/blob/ef6941df5b94997f79b429347c5d9b84e600bdd3/psycopg/psycopg/_encodings.py#L100-L101

which is a wrapper for PQparameterStatus:
https://www.postgresql.org/docs/current/libpq-status.html#LIBPQ-PQPARAMETERSTATUS
(so that the setting can be retrieved without running a query).

Maybe the way you are connecting via psql sets the client_encoding?
Can you try to get the result of `SHOW client_encoding` from psycopg?