Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances - Mailing list pgsql-admin

From Ashesh Vashi
Subject Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances
Date
Msg-id CAG7mmoz+71Uk1FWGr40jk8mmYOkNuFGRHhjyrmgzXr2V4avJRQ@mail.gmail.com
Whole thread Raw
In response to Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
On Fri, Feb 8, 2019 at 1:58 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
I wrote:
>> This looks like a pgadmin bug ...

> Looking at it, I'm betting somebody thought this was a cute way to
> set bytea_output if it exists, without getting a failure on servers
> too old to have it.  We added that in 9.0, so maybe it's not quite
> old enough to make it a moot point; but failing on RO servers is
> not nice either.  Anyway, yeah, it's pgadmin's problem to fix.

Better idea:

select set_config('bytea_output','escape',false) from pg_settings where name = 'bytea_output';
Thanks for the solution - Tom.
We will fix that in that in pgAdmin.

-- Thanks, Ashesh

This is depressingly lacking in safe schema-qualification, btw.

                        regards, tom lane

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances
Next
From: Jeremiah Bauer
Date:
Subject: Postgres Database Disk Usage