Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vWfaO-00727N-1q for pgsql-general@arkaria.postgresql.org; Fri, 19 Dec 2025 18:52:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vWfaN-008kvY-1U for pgsql-general@arkaria.postgresql.org; Fri, 19 Dec 2025 18:52:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vWfaN-008kvP-0T for pgsql-general@lists.postgresql.org; Fri, 19 Dec 2025 18:52:19 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vWfaL-001dxW-1F for pgsql-general@lists.postgresql.org; Fri, 19 Dec 2025 18:52:19 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 5BJIqECD3360048; Fri, 19 Dec 2025 13:52:14 -0500 From: Tom Lane To: Igor Korot cc: "pgsql-generallists.postgresql.org" Subject: Re: Fwd: PQexecPrepared() question In-reply-to: References: <2547700.1765940917@sss.pgh.pa.us> <9a0ce31a49f149d8d982d2b359095560655f781e.camel@cybertec.at> Comments: In-reply-to Igor Korot message dated "Fri, 19 Dec 2025 10:49:26 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3360046.1766170334.1@sss.pgh.pa.us> Date: Fri, 19 Dec 2025 13:52:14 -0500 Message-ID: <3360047.1766170334@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Igor Korot 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). regards, tom lane