| From: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
|---|---|
| To: | "Robert J(dot) Rotter" <rotter(at)denic(dot)de> |
| Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: Cannot connect to Replication Slave with the new Version 4.2 of PGAdmin4 |
| Date: | 2019-02-08 04:52:53 |
| Message-ID: | CAG7mmoxd5CgFhO-RoxWDxq9SwpyvQu-Su5+cZq_dk7Bz+HVcjA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Thu, Feb 7, 2019 at 9:24 PM Robert J. Rotter <rotter(at)denic(dot)de> wrote:
> Hi,
>
> I updated to the new version 4.2 of pgAdmin4.
>
> Suddenly I cannot connect to a Replication Slave anymore.
>
> Error is: "Cannot execute Select in a read-only transaction"
>
> With 4.1 there is no such problem. Have you experienced this also?
>
Looks likes a bug introduced in last release.
Thanks for the report.
I have created a bug #3973 <https://redmine.postgresql.org/issues/3973>.
And - fixed as suggested by Tom:
https://www.postgresql.org/message-id/25473.1549571318%40sss.pgh.pa.us
--
Thanks & Regards,
Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company
<http://www.enterprisedb.com/>
*http://www.linkedin.com/in/asheshvashi
<http://www.linkedin.com/in/asheshvashi>*
>
>
> Regards
>
> R.J.Rotter
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zoltán Sörös | 2019-02-08 13:23:00 | pgAdmin 4 V4.2 and non-unicode database |
| Previous Message | Ashesh Vashi | 2019-02-08 04:24:54 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |