| From: | Souvik Chatterjee <chatterjeesouvik(dot)besu(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17615: Getting error while inserting records in the table: invalid byte sequence for encoding "UTF8": 0xae |
| Date: | 2022-09-16 15:48:52 |
| Message-ID: | CAHE6XHZj02LQQ5HUUsUkF=oM5kvshMPk6tTwgHPJbw2DzsPBFg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
So you meant to say registered trademark: ®
is not a valid UTF-8 character?
Seems strange to me.
regards,
Souvik Chattopadhyay
On Fri, 16 Sept 2022, 08:39 Tom Lane, <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-09-16 16:06:07 | Re: BUG #17615: Getting error while inserting records in the table: invalid byte sequence for encoding "UTF8": 0xae |
| Previous Message | Julien Rouhaud | 2022-09-16 14:36:12 | Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work. |