Re: BUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby
Date
Msg-id 494.1550613106@sss.pgh.pa.us
Whole thread Raw
In response to BUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> I have pgAdmin 4.2 installed on my windows machine.  I am trying to connect
> to our hot standby server with pgAdmin and I get the following Error:
> ERROR: cannot execute SELECT in a read-only transaction

> My DBA has indicated that when I attempt to connect to the server I am
> attempting the following SQL:

> < 2019-02-19 14:14:04.578 EST > STATEMENT:  SET DateStyle=ISO; SET
> client_min_messages=notice;UPDATE pg_settings SET setting = 'escape'   
> WHERE name = 'bytea_output';SET client_encoding='UNICODE';

Yeah, this is a previously-reported pgAdmin bug: it shouldn't be using
that query when it doesn't yet know if the target server is read-only.
You'd have to go ask on their mailing lists as to what the timetable for
fixing it is.

            regards, tom lane


pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name
Next
From: Michael Paquier
Date:
Subject: Re: Segmentation Fault in logical decoding get/peek API