From: | "Bawol, Brian" <brian(dot)bawol(at)freightverify(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
Date: | 2019-02-07 19:01:23 |
Message-ID: | CAF56UXJKGwgA45ejrZCUqgpmRvt0UQQ83ku-UVESaRJ9pg8ktw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support pgsql-admin |
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?
On Thu, Feb 7, 2019 at 1:47 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Bawol, Brian" <brian(dot)bawol(at)freightverify(dot)com> writes:
> > My co-worker and I are both receiving the following error message when
> > attempting to connect to AWS Postgres 10.4 (and 10.6) database instances
> > using PgAdmin 4.2:
>
> > "ERROR: cannot execute SELECT in a read-only transaction"
>
> That seems pretty strange. What's the actual underlying query that's
> failing? (The server log should show that, as a appendage to the
> occurrence of this error, even if PgAdmin won't tell you.)
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-02-07 19:56:05 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
Previous Message | Tom Lane | 2019-02-07 18:47:48 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
From | Date | Subject | |
---|---|---|---|
Next Message | Pepe TD Vo | 2019-02-07 19:43:43 | Re: insert aborted commands ignored |
Previous Message | Tom Lane | 2019-02-07 18:47:48 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |