From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Bawol, Brian <brian.bawol@freightverify.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
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, 7 Feb 2019 16:56:05 -0300
Message-ID: <20190207195605.GA14960@alvherre.pgsql> (raw)
In-Reply-To: <CAF56UXJKGwgA45ejrZCUqgpmRvt0UQQ83ku-UVESaRJ9pg8ktw@mail.gmail.com>
On 2019-Feb-07, Bawol, Brian wrote:
> It looks like this is the query that occurs at the same time:
>
> STATEMENT: SET DateStyle=ISO; SET client_min_messages=notice;UPDATE
> pg_settings SET setting = 'escape' WHERE name = 'bytea_output';SET
> client_encoding='UNICODE';
>
> Does this help?
Ah, so pgadmin 4.2 is trying to set bytea_output, which is disallowed;
the reason it says "cannot execute SELECT" is that the UPDATE for the
view is turned into a "SELECT set_config()" by a view rule.
That makes sense. This looks like a pgadmin bug ...
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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: alvherre@2ndquadrant.com, brian.bawol@freightverify.com, tgl@sss.pgh.pa.us, 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: <20190207195605.GA14960@alvherre.pgsql>
* 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