Thread: BUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby

The following bug has been logged on the website:

Bug reference:      15643
Logged by:          Eric Katchan
Email address:      eric.katchan+postgres@concordia.ca
PostgreSQL version: 9.6.9
Operating system:   Linux
Description:

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';

Any ideas?

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