Re: ERROR: invalid byte sequence for encoding

2018-01-15 Thread André Burkhardt
Hi, thank you for your response. After searching for existing Bugreports/Issues on https://redmine.postgresql.org/projects/pgadmin4/issues I found one, whose description matches to the problems we have. https://redmine.postgresql.org/issues/2885 We also have the option standard_conforming_string

Re: ERROR: invalid byte sequence for encoding

2018-01-15 Thread Murtuza Zabuawala
Hi, Postgres database server is throwing an error while executing the sql to fetch table definition, please report a bug here Link Please add the steps/details required to re-produce the issue on developer's machine along with sample table

Re: ERROR: invalid byte sequence for encoding

2018-01-15 Thread Murtuza Zabuawala
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,

ERROR: invalid byte sequence for encoding

2018-01-15 Thread André Burkhardt
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