Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1groiM-0005KU-Fr for pgsql-admin@arkaria.postgresql.org; Thu, 07 Feb 2019 18:47:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1groiJ-0002xM-HZ for pgsql-admin@arkaria.postgresql.org; Thu, 07 Feb 2019 18:47:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1groiJ-0002wg-2C for pgsql-admin@lists.postgresql.org; Thu, 07 Feb 2019 18:47:55 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1groiF-0000ip-Kb for pgsql-admin@lists.postgresql.org; Thu, 07 Feb 2019 18:47:52 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x17IlmTi013860; Thu, 7 Feb 2019 13:47:48 -0500 From: Tom Lane To: "Bawol, Brian" cc: pgsql-admin@lists.postgresql.org Subject: Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances In-reply-to: References: Comments: In-reply-to "Bawol, Brian" message dated "Thu, 07 Feb 2019 12:54:00 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13858.1549565268.1@sss.pgh.pa.us> Date: Thu, 07 Feb 2019 13:47:48 -0500 Message-ID: <13859.1549565268@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "Bawol, Brian" 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