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 02:17:35 |
Message-ID: | CAHE6XHZZnQgQaVopmRyPc_LFJcZh41Pd+TGGcsDqUAJwE_y1tQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
We have set the client encoding to UTF-8, but still error is coming.
This is getting saved properly in Oracle databases, then what's the issue
postgres?
regards,
Souvik Chattopadhyay
On Fri, 16 Sept 2022, 01:03 Tom Lane, <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> PG Bug reporting form <noreply(at)postgresql(dot)org> 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-09-16 03:09:10 | Re: BUG #17615: Getting error while inserting records in the table: invalid byte sequence for encoding "UTF8": 0xae |
Previous Message | Peter Geoghegan | 2022-09-15 22:39:25 | Re: PANIC in heap_delete during ALTER TABLE |