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 1i2jWs-0005tG-Qd for pgsql-admin@arkaria.postgresql.org; Tue, 27 Aug 2019 22:01:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i2jWp-0006uw-9I for pgsql-admin@arkaria.postgresql.org; Tue, 27 Aug 2019 22:01:27 +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 1i2jWo-0006un-I5 for pgsql-admin@lists.postgresql.org; Tue, 27 Aug 2019 22:01:27 +0000 Received: from sonic301-32.consmr.mail.ne1.yahoo.com ([66.163.184.201]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i2jWh-0007Z8-Uk for pgsql-admin@postgresql.org; Tue, 27 Aug 2019 22:01:26 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1566943276; bh=93HbsWF12qknD4uiERYOXmbfuM7n60eS3Ter0c6Ask0=; h=Date:From:To:Subject:References:From:Subject; b=m5Ym6nShH56HMHYRZzmjn9Erkz9jlYBhC6SzPSxRdrPcGw+4kHP4vKJo5aTQWoZTKGr9KU6Hpls4TLLmvd/PokUk8JIkp2nlTwOsxZmeJKsNDjriStAn78O3vd6LecNauNSVQFF/O+9Wr9Tf86kiejl6By1d9UBD+QOx6aKs5sRViJ53ieYc2/X33t+Xqn/6WKVPTyMB9F9hXJ4OC2228nPcbSjtZSlpXMwgtrrjA+OEGo9sF7e2gESbTayKs9sJuM6SqUiYoadDo5TWIPIyo3l6SmM6s67rfRgvWlMbZM/gcApGfvWWKp1Y9jSuAtQnvVxfjGPTPDEmyGxbXxZ+rw== X-YMail-OSG: F5HquXIVM1mYzqJ_axBBFnrQbmdsv.1tDtGoMBdhDl_zYdKhBUZTBpNyxq3a1gA dD8SzDLuMfg5H5.GPaOtAN6CH4ukn6bUw_HHvW3hJb1O.tQm3nbZfO31CLjrxVgcI9fwLjnxsQwv ogZLQlMw0x6Zw1mE2VzJp2uXJDMz0ZjSkMa9pjdV.Er8DgMOCIU4pSMQ0pmjkfCXQxSogkdAtUoC Jov5GjzE.PDZgO.f3iPEt1jvb6jZkUe_i1k0dC0LLIgv5_mbLCKNfy7XcUWPXJNv6K_0pULshzwd e.D1iiYBOUsVBrOeBCZjaX2tPf.oT0Rul8tPBbrvXAFnSn4KAUT9hAowq_nPSAIp7zU5H7vjLgYZ XMG1eBLnzmf5_BD7T1.vxbRe7gbNUWPt4y97WvtC74xgK_Yrm7GI.4qacHvC2Jy6Z9u9VLDALW8_ ba6VnB7Hil8ZW20cHENiEEto_lmWdJ_OMnptPxqnTvEiTa1TxftFD2wrHVAtGJtv7v0.ni5yKbOs KFXVzCrOq0Ay87r20EXV.pIVxOTBl6MerX9Uju.6kLDGDCAdUC.qnzc_ijg626GJZh7Uv48VysXU Alc1h5LkCVBo_SwmHt3_6ZOmDsc8rcWzdtjGEwwS8NdWAVACdvqoT1RqKDIoeEDeeN0mVuEa7zSC k2sc7760U1.hFYs80UImGZw_b3GEKPOdyaAoduwRzq9sslQVSetQdMqSAEsWTcTtqTq.b5mBf3.u x1y3saWMzfKbYXL3KxULoXelOLefXSzSM_nYMn0rXKA.EEl6aFv3WHKLfnIh3EUS9T5w6MrwxI25 c301MPUK4KVikB3YqcjsHYTfaF9Q1By3djrlqGJOPtgcAK5rsRHu4M.CwJBrpcSvsq9CH172RX3q OWrJfrlBtFKuwXlnMI30kwGqLtaZKVf53NBlk7pOxGdORZfOWXkr7TgRANLWgDrviU_6kwp2Flu_ 762HSa4TI0gV5Hi6bHnimr80vOXI8EkqWI.3pkD4mZq4xULA.uEvsGK8osCoBHxrONIbGInLxGWI P90kHB9PRZ6FTRpbPLCkZGNH0aifZKV3.uBrsk8OV_FsDHbCBdnXX8y8njD2TDTy2JzKmqWc6S9k 7g_0k0_S9kMGUJnTMa28_ySg_wafKZmcAmy431gpKckzx.mruq2_dF_3mScCCq7HY.dODahVdRck gp6vljt5Pcl_TvJOuYC8bViEKLBVWK4JtqoxhVuvVcbd4boyXoIQ0UanbvpZRErdxuhkeAWKBbCb 6pSftqRdXT0gnLGE- Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.ne1.yahoo.com with HTTP; Tue, 27 Aug 2019 22:01:16 +0000 Date: Tue, 27 Aug 2019 22:01:11 +0000 (UTC) From: Andy Hsu To: "pgsql-admin@postgresql.org" Message-ID: <2116891825.115840.1566943271674@mail.yahoo.com> Subject: Disable sending query to obtain database performance information from pgAdmin4 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_115839_1173792455.1566943271673" References: <2116891825.115840.1566943271674.ref@mail.yahoo.com> X-Mailer: WebService/1.1.14253 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36 Content-Length: 1580 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_115839_1173792455.1566943271673 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit All, We have used pgAdmin III for Greenplum database, postgresql 8.2. Recently, we upgraded to Greenplum postgresql 8.3 and switched to pgAdmin4. We found that pgAdmin4 sends many sqls to obtain database performance, which filled up Greenplum log quickly. I cannot find anywhere to disable these queries. Please advise on where and how to disable? Thanks,Andy ------=_Part_115839_1173792455.1566943271673 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
All,

We have used pgAdmin III for Greenplum database, postgresql 8.2. Recently, we upgraded to Greenplum postgresql 8.3 and switched to pgAdmin4.

We found that pgAdmin4 sends many sqls to obtain database performance, which filled up Greenplum log quickly.

I cannot find anywhere to disable these queries. Please advise on where and how to disable?

Thanks,
Andy
------=_Part_115839_1173792455.1566943271673--