From: Tom Lane <tgl@sss.pgh.pa.us>
To: Souvik Chatterjee <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: 
 <CAHE6XHZZnQgQaVopmRyPc_LFJcZh41Pd+TGGcsDqUAJwE_y1tQ@mail.gmail.com>
References: <17615-6d24c25ba0e8a9e6@postgresql.org>
 <3421821.1663270405@sss.pgh.pa.us>
 <CAHE6XHZZnQgQaVopmRyPc_LFJcZh41Pd+TGGcsDqUAJwE_y1tQ@mail.gmail.com>
Comments: In-reply-to Souvik Chatterjee <chatterjeesouvik.besu@gmail.com>
	message dated "Fri, 16 Sep 2022 07:47:35 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3551123.1663297750.1@sss.pgh.pa.us>
Date: Thu, 15 Sep 2022 23:09:10 -0400
Message-ID: <3551124.1663297750@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3551124.1663297750%40sss.pgh.pa.us>
Precedence: bulk

Souvik Chatterjee <chatterjeesouvik.besu@gmail.com> writes:
> We have set the client encoding to UTF-8, but still error is coming.

That is exactly what you *shouldn't* do, because the data you are sending
is evidently not in UTF8.  It's probably some LATINn variant.

> This is getting saved properly in Oracle databases, then what's the issue
> postgres?

[ shrug... ]  It's likely a matter of what software stack you have on
the client side, not which server you're using exactly.

			regards, tom lane