| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Bawol, Brian" <brian(dot)bawol(at)freightverify(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)lists(dot)postgresql(dot)org, pgadmin-support(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| Date: | 2019-02-07 19:56:05 |
| Message-ID: | 20190207195605.GA14960@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-02-07 20:23:21 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| Previous Message | Bawol, Brian | 2019-02-07 19:01:23 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-02-07 20:23:21 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| Previous Message | Pepe TD Vo | 2019-02-07 19:43:43 | Re: insert aborted commands ignored |