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 1grpmR-00089x-Ff for pgadmin-support@arkaria.postgresql.org; Thu, 07 Feb 2019 19:56:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1grpmO-0003wc-8h for pgadmin-support@arkaria.postgresql.org; Thu, 07 Feb 2019 19:56:12 +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 1grpmN-0003wO-RG for pgadmin-support@lists.postgresql.org; Thu, 07 Feb 2019 19:56:12 +0000 Received: from mail-qt1-x844.google.com ([2607:f8b0:4864:20::844]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grpmK-0002Bi-Ci for pgadmin-support@lists.postgresql.org; Thu, 07 Feb 2019 19:56:10 +0000 Received: by mail-qt1-x844.google.com with SMTP id n32so1284567qte.11 for ; Thu, 07 Feb 2019 11:56:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=NQNxcUyG4JYaaaWd0ADD0t444ymrE1Tc8v9whg4xqQs=; b=lxUdUwu9shqPu6wW08JNfgU6g2qVhYHV42JgKcXBd61zbW7rTPcba7OkfEkzujte3s /fYVRv+kYF7BAUdzXeeT2QYZ2MqdLKLZoeiFV5jZUroCAcohA/2uh3pMCDGnmIOVD5CK Wp+vDtwOZYOq0XM02O09ePSTf2OL5CWNX5VHFqwnJ4cwUMIEdPGjB7ztDwve3txgw8F5 zAqmv84ha3nyuNAZD91gxITnmeyvLTQV/n+gn4NYqNkXeQ7J69MQfNsBTU69ToaIj9s0 nb+In5qhRnD1S2yB1RMyTCNhF+leHzjvmC76U5drfefk+mlyTjpMcmrZdOwiogsPggwF rH2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=NQNxcUyG4JYaaaWd0ADD0t444ymrE1Tc8v9whg4xqQs=; b=HEDhaOGgi7f5dVvWUDC54v3+Zm9TLbjRm+XcRHeMf/dmvRt5iaRECI4hQr2Wd+atgo HBGWEBGfE7CJ3LWH+Cox0DfIY4f6p5A14I7bclArgqeDZievu1R2fduzNQLAO9SQsHfP 5AF4p10TfNRbWvPgVZCK86WW4d2H2fEUuER7+un8nxj9VG4c/C9rqfdvnfq7uAeJHtrc ZqlvA2Z6yMTloBNiU9VYfTLiYlMkuxNnGJBV1vCkmY0QXQKp5iO1tEuHxMmHbxshlexO klMeqqfCknWji+RgShf9pt563k5WoYtxDqCV+fYfZVOJJReAVNaMZnt48GUrZobxSvEs 6KnQ== X-Gm-Message-State: AHQUAua0ewXhDB2y2TO1tnQWgdVfaAYmcj+bk4b8BQeXWEWKOWu29Lfq wJtAikdh6wMAsHsyZkq+tfOl0g== X-Google-Smtp-Source: AHgI3IY36FkD1y8RRr/pu0aj7gM4HeqML0kBt4ijGJIqtuSZjUMng3aY0Mu2cH9afMQ3SMMo13PhyQ== X-Received: by 2002:ac8:3770:: with SMTP id p45mr5188120qtb.275.1549569367531; Thu, 07 Feb 2019 11:56:07 -0800 (PST) Received: from nimloth.alvh.no-ip.org ([201.186.80.67]) by smtp.gmail.com with ESMTPSA id 20sm24342572qtp.54.2019.02.07.11.56.06 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 07 Feb 2019 11:56:07 -0800 (PST) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 5809112026E; Thu, 7 Feb 2019 16:56:05 -0300 (-03) Date: Thu, 7 Feb 2019 16:56:05 -0300 From: Alvaro Herrera To: "Bawol, Brian" Cc: Tom Lane , pgsql-admin@lists.postgresql.org, pgadmin-support@lists.postgresql.org Subject: Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances Message-ID: <20190207195605.GA14960@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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? Ah, so pgadmin 4.2 is trying to set bytea_output, which is disallowed; the reason it says "cannot execute SELECT" is that the UPDATE for the view is turned into a "SELECT set_config()" by a view rule. That makes sense. This looks like a pgadmin bug ... -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services