From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | eric(dot)katchan+postgres(at)concordia(dot)ca |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15643: Problem using PGAdmin 4.2 to connect to postrgres hot standby |
Date: | 2019-02-19 21:51:46 |
Message-ID: | 494.1550613106@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-02-20 02:09:11 | Re: Segmentation Fault in logical decoding get/peek API |
Previous 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 |