From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | ericwilfried(dot)ettien(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17895: Bug concerning UTF-8 |
Date: | 2023-04-14 03:00:20 |
Message-ID: | 20230414.120020.700230983061721139.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
At Thu, 13 Apr 2023 12:32:11 +0000, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote in
> In fact when i created databse with default value UTF-8 i received this
> error : 'utf-8' codec can't decode byte 0xf4 in position 8: invalid
> continuation byte.
> So i explored solution and i used this link:
> https://stackoverflow.com/questions/45897521/postgresql-utf8-codec-cant-decode-byte-0xe9-in-position-42-invalid-continua.
> However this error is the same.
> Please i would like to have solution concerning this error.
As someone mentioned in the thread, this is not an issue of PostgreSQL.
I am not at all familiar with the details of pgAdmin, but I surmise
that the error message indicates that the characters you entered, or
the ones sent by PostgreSQL, do not match the encoding that pgAdmin
expects. It would be worthwhile to ensure that the language settings
of pgAdmin are consistent with the connected database and local
environment. For further assistance, you should consult the pgAdmin
team.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Eric Wilfried Ettien | 2023-04-14 10:06:38 | Re: BUG #17895: Bug concerning UTF-8 |
Previous Message | fjz22 | 2023-04-13 16:47:15 | 9. PostgreSQL Server 15.2 Subprocess Went down at function 'expanded_record_set_fields' |