Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oYucB-0007jN-CV for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Sep 2022 19:33:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oYuc9-0001nC-Rl for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Sep 2022 19:33:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oYuc9-0001ml-K6 for pgsql-bugs@lists.postgresql.org; Thu, 15 Sep 2022 19:33:33 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oYuc3-0004bQ-CS for pgsql-bugs@lists.postgresql.org; Thu, 15 Sep 2022 19:33:28 +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 28FJXPsL3421822; Thu, 15 Sep 2022 15:33:25 -0400 From: Tom Lane To: chatterjeesouvik.besu@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17615: Getting error while inserting records in the table: invalid byte sequence for encoding "UTF8": 0xae In-reply-to: <17615-6d24c25ba0e8a9e6@postgresql.org> References: <17615-6d24c25ba0e8a9e6@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Thu, 15 Sep 2022 16:24:13 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3421820.1663270405.1@sss.pgh.pa.us> Date: Thu, 15 Sep 2022 15:33:25 -0400 Message-ID: <3421821.1663270405@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > Getting the below error while inserting records into the table: > invalid byte sequence for encoding "UTF8": 0xae That is, in fact, an invalidly-encoded character per UTF8 rules, so I see no reason to think there is any Postgres bug here. What's more likely is that you haven't set client_encoding to match the encoding of the data you're trying to insert. regards, tom lane