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 1grqHx-00018x-N7 for pgadmin-support@arkaria.postgresql.org; Thu, 07 Feb 2019 20:28:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1grqHw-00059R-9E for pgadmin-support@arkaria.postgresql.org; Thu, 07 Feb 2019 20:28:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grqHw-00059H-3i; Thu, 07 Feb 2019 20:28:48 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grqHq-0000QI-0k; Thu, 07 Feb 2019 20:28:47 +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 x17KScbu025474; Thu, 7 Feb 2019 15:28:38 -0500 From: Tom Lane To: Alvaro Herrera cc: "Bawol, Brian" , pgsql-admin@lists.postgresql.org, pgadmin-support@lists.postgresql.org Subject: Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances In-reply-to: <25216.1549571001@sss.pgh.pa.us> References: <20190207195605.GA14960@alvherre.pgsql> <25216.1549571001@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Thu, 07 Feb 2019 15:23:21 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25472.1549571318.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 07 Feb 2019 15:28:38 -0500 Message-ID: <25473.1549571318@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 failing on RO servers is > not nice either. Anyway, yeah, it's pgadmin's problem to fix. Better idea: select set_config('bytea_output','escape',false) from pg_settings where na= me =3D 'bytea_output'; This is depressingly lacking in safe schema-qualification, btw. regards, tom lane