Re: [pgadmin-hackers] PATCH: To fix the issue in Database node (pgAdmin4) - Mailing list pgadmin-hackers

Hi

On Wed, Jan 25, 2017 at 12:21 PM, Murtuza Zabuawala
<murtuza.zabuawala@enterprisedb.com> wrote:
> Hi Dave,
>
> Last patch had Python-3 fix for test suite, but now it is already committed.
> PFA updated patch.

It still doesn't work completely for me. I tried changing the value of
bytea_output in a database that *does* allow connections, and I get a
503 response from the server, with a message of:

{"info":"CONNECTION_LOST","errormsg":"Connection to the server has
been lost!","data":{"database":null,"conn_id":null,"sid":1},"result":null,"success":0}

The payload sent via PUT to
http://127.0.0.1:5050/browser/database/obj/1/1/12403 was:

{"id":12403,"variables":{"changed":[{"role":"pgweb","name":"bytea_output","value":"hex","database":"postgres"}]}}

It works fine without the patch applied.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company