PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID15643
PG Version9.6.9
OSLinux
Opened2019-02-19 20:46:19+00
Reported byEric Katchan
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      15643
Logged by:          Eric Katchan
Email address:      (redacted)
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?

Messages

DateAuthorSubject
2019-02-19 20:46:19+00PG Bug reporting formBUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby
2019-02-19 21:51:46+00Tom LaneRe: BUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby