| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Bawol, Brian" <brian(dot)bawol(at)freightverify(dot)com> |
| 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 18:47:48 |
| Message-ID: | 13859.1549565268@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-admin |
"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 | Bawol, Brian | 2019-02-07 19:01:23 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| Previous Message | Bawol, Brian | 2019-02-07 17:54:00 | PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bawol, Brian | 2019-02-07 19:01:23 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| Previous Message | Bawol, Brian | 2019-02-07 17:54:00 | PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |