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

From PG Bug reporting form
Subject BUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby
Date
Msg-id 15643-944c1ac9f8108278@postgresql.org
Whole thread Raw
Responses Re: BUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
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?


pgsql-bugs by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name
Next
From: David Rowley
Date:
Subject: Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name