From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Bawol, Brian <brian.bawol@freightverify.com>
Cc: pgsql-admin@lists.postgresql.org
Cc: pgadmin-support@lists.postgresql.org
Subject: Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances
Date: Thu, 07 Feb 2019 15:28:38 -0500
Message-ID: <25473.1549571318@sss.pgh.pa.us> (raw)
In-Reply-To: <25216.1549571001@sss.pgh.pa.us>
References: <20190207195605.GA14960@alvherre.pgsql>
<25216.1549571001@sss.pgh.pa.us>
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';
This is depressingly lacking in safe schema-qualification, btw.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, brian.bawol@freightverify.com, pgsql-admin@lists.postgresql.org, pgadmin-support@lists.postgresql.org
Subject: Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances
In-Reply-To: <25473.1549571318@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox