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

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: eric(dot)katchan+postgres(at)concordia(dot)ca
Subject: BUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby
Date: 2019-02-19 20:46:19
Message-ID: 15643-944c1ac9f8108278@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 15643
Logged by: Eric Katchan
Email address: eric(dot)katchan+postgres(at)concordia(dot)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?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2019-02-19 20:57:19 Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name
Previous Message Julien Rouhaud 2019-02-19 20:21:42 Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name