Re: ERROR: invalid byte sequence for encoding
От | Murtuza Zabuawala |
---|---|
Тема | Re: ERROR: invalid byte sequence for encoding |
Дата | |
Msg-id | CAKKotZRHyyk1y3dHaG4TEZJ9kL-TekLP_53VYdGLSmYU1x6LBA@mail.gmail.com обсуждение исходный текст |
Ответ на | ERROR: invalid byte sequence for encoding (André Burkhardt <andre.burkhardt@uni-jena.de>) |
Ответы |
Re: ERROR: invalid byte sequence for encoding
|
Список | pgadmin-support |
Hi,
Could you please provide pgAdmin4.log file with debug mode on.
For more information check: https://www.pgadmin.org/faq/#8
(Rename/delete your previous log file, once you set the debug mode, try to re-produce the issue in pgAdmin4 again and send us the log file)
Also provide below information,
1) Are you running pgAdmin4 as Desktop mode or Web mode?
2) Postgres server version
3) OS details
--
Regards,
On Mon, Jan 15, 2018 at 4:24 PM, André Burkhardt <andre.burkhardt@uni-jena.de> wrote:
We are using pgAdmin 4 2.0/2.1. Allmost all of our databases using
Encoding LATIN1. We have the problem, that when we want to show a table
definition in the SQL-Tab, an error message pops up:
Error retrieving the information - INTERNAL SERVER ERROR
ERROR: invalid byte sequence for encoding "LATIN1":0x00
Here some output:
show client_encoding;
client_encoding
-------------------
UNICODE
show server_encoding;
server_encoding
------------------
LATIN1
show lc_collate;
lc_collate
-------------
de_DE
Is there an solution?
В списке pgadmin-support по дате отправления: