I've asked the Debian/Ubuntu package maintainer to look into this.
On Fri, Apr 20, 2018 at 10:23 AM, frankgard <frank.von.postgresql.org@familie-gard.de> wrote:Hi Tony, according to this Stackoverflow post <https://stackoverflow.com/questions/49919149/unable-to-connect-to-postgresql-with-pgadmin4-readonly-attribute-error> , the error seems to be caused by a too old psycopg2 library. Perhaps you can upgrade to v2.7, or just comment out line 313 of /usr/share/pgadmin4/web/pgadmin/utils/driver/psycopg2/connection.py as some kind of "dirty hack", but be aware that I don't know the "deeper consequences" of doing so. Hope this helps. Cheers, Frank. -- Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html-- Dave PageBlog: http://pgsnake.blogspot.comTwitter: @pgsnakeEnterpriseDB UK: http://www.enterprisedb.comThe Enterprise PostgreSQL Company
Hi Tony, according to this Stackoverflow post <https://stackoverflow.com/questions/49919149/unable-to-connect-to-postgresql-with-pgadmin4-readonly-attribute-error> , the error seems to be caused by a too old psycopg2 library. Perhaps you can upgrade to v2.7, or just comment out line 313 of /usr/share/pgadmin4/web/pgadmin/utils/driver/psycopg2/connection.py as some kind of "dirty hack", but be aware that I don't know the "deeper consequences" of doing so. Hope this helps. Cheers, Frank. -- Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html
pgadmin-support by date:
Соглашаюсь с условиями обработки персональных данных
