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 1j5YPM-0005Hp-TN for pgsql-admin@arkaria.postgresql.org; Sat, 22 Feb 2020 17:17:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j5YPK-0004fN-Ta for pgsql-admin@arkaria.postgresql.org; Sat, 22 Feb 2020 17:17:38 +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 1j5YPJ-0004fC-2P; Sat, 22 Feb 2020 17:17:38 +0000 Received: from [66.111.4.25] (helo=out1-smtp.messagingengine.com) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j5YPE-0004t7-57; Sat, 22 Feb 2020 17:17:36 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 0C2CC21B5A; Sat, 22 Feb 2020 12:17:20 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sat, 22 Feb 2020 12:17:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=w fFNDjkcfpyTRDdIXVkYUxwOhSZSycWgp7cgP7+PUho=; b=DZNuUTq7WqIgmsgTF 0RN8r+btE6O1kUoCrfBos+XlwoFH/47ZNIqPL3IIIpHX2iuWZTB7R4cEbDwUi5SX ERnqK+Dldlbg0tfTsVLYGhsIrOEeIJ/E5DkP/wPC7l5cWixOcHzqcTyac+mmYlBx l3KbgniSEsBevh9fcGKfQt9/Yww4pQUquEJBbXBfztCjluy98d7D/X6hETyAxsxF CS7U7lvxHm5BoMZb6ep3DbEuMnhG1VmSxW6B3ajigUfABXbb+I2fuB/pSZ2b/GjO mdlaZWJWDvotWR1lcqT4Oz96j2u0397KBhSVqGiNSTd9T89H+FYMYd2hl/5PTsui Ba9lQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=wfFNDjkcfpyTRDdIXVkYUxwOhSZSycWgp7cgP7+PU ho=; b=vOzYKk+C12NUBQyA0SMDnXJxSl8fQddxhUmHWUEVK+7hWM3gvfXyGZYCZ /OANO/l0KP5tCqKpkTjO5/ZArzTIqBwKrqpRpGfLUdlDmTZXzZ7PPKxfugPJloAQ zB2ew4gtaTHUFzykKbx5KiAdEdQKH5ESfBaoWuzY0hzO+OH95Tzw8h+/bKCwDCbA c0+L5DS+YLNsVo53QS4Guz2Rk/87+VUtDDlO6iaqfJtykJSqXxe3ApAEUbBaG1jW DUeKmmti++ZbR+VcHi4jnnIThhkjKRc+cxFRwqJBfJbDOOpc8TbomWrzNHkz8Clz K0ktQJvC1byUMs8is/6Oo6L+nZvKg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrkeeigddutddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgnecukfhppeejuddrvddu vddruddvledrudelfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Received: from [192.168.1.10] (unknown [71.212.129.193]) by mail.messagingengine.com (Postfix) with ESMTPA id 500D93060BE4; Sat, 22 Feb 2020 12:17:19 -0500 (EST) Subject: Re: Reset DB stats suggestion pg_stat_reset() To: postggen2020 s , pgsql-general@postgresql.org, pgsql-admin@postgresql.org References: From: Adrian Klaver Message-ID: Date: Sat, 22 Feb 2020 09:17:18 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 66.111.4.25 (deferred) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2/22/20 12:26 AM, postggen2020 s wrote: > Hi Team, > > Good Afternoon, > > We have seen some deadlocks and tempfile count in pg_stat_database view. > We are trying to reset the stats. > Can we use pg_stat_reset() function to reset these stats without any > impact stats of databases. > Please advise the process to reset the stats. See here: https://www.postgresql.org/docs/12/monitoring-stats.html Table 27.20. Additional Statistics Functions It details what your options are. > > Thanks. > Postggen. -- Adrian Klaver adrian.klaver@aklaver.com