The pgAdmin Development Team are pleased to announce pgAdmin 4 version 4.2.
This release of pgAdmin 4 includes over 40 bug fixes. For
more details please see the release notes at:
https://www.pgadmin.org/docs/pgadmin4/dev/release_notes_4_2.html.
pgAdmin is the leading Open Source graphical ma
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?
Regards
R.J.Rotter
On 2019-Feb-07, Bawol, Brian wrote:
> It looks like this is the query that occurs at the same time:
>
> STATEMENT: SET DateStyle=ISO; SET client_min_messages=notice;UPDATE
> pg_settings SET setting = 'escape'WHERE name = 'bytea_output';SET
> client_encoding='UNICODE';
>
> Does this help?
A
Alvaro Herrera writes:
> On 2019-Feb-07, Bawol, Brian wrote:
>> It looks like this is the query that occurs at the same time:
>> STATEMENT: SET DateStyle=ISO; SET client_min_messages=notice;UPDATE
>> pg_settings SET setting = 'escape'WHERE name = 'bytea_output';SET
>> client_encoding='UNICODE
I wrote:
>> This looks like a pgadmin bug ...
> Looking at it, I'm betting somebody thought this was a cute way to
> set bytea_output if it exists, without getting a failure on servers
> too old to have it. We added that in 9.0, so maybe it's not quite
> old enough to make it a moot point; but fa
On Fri, Feb 8, 2019 at 1:58 AM Tom Lane wrote:
> I wrote:
> >> This looks like a pgadmin bug ...
>
> > Looking at it, I'm betting somebody thought this was a cute way to
> > set bytea_output if it exists, without getting a failure on servers
> > too old to have it. We added that in 9.0, so maybe
On Thu, Feb 7, 2019 at 9:24 PM Robert J. Rotter 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
