Souvik Chatterjee <chatterjeesouvik(dot)besu(at)gmail(dot)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