Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oiter-0006cf-0c for pgsql-performance@arkaria.postgresql.org; Thu, 13 Oct 2022 08:33:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oitep-00044K-QI for pgsql-performance@arkaria.postgresql.org; Thu, 13 Oct 2022 08:33:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oitep-000448-E1 for pgsql-performance@lists.postgresql.org; Thu, 13 Oct 2022 08:33:35 +0000 Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oitek-0007Lz-Vy for pgsql-performance@postgresql.org; Thu, 13 Oct 2022 08:33:35 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com; s=20170201; h=In-Reply-To:Content-Type:MIME-Version:References:Reply-To: Message-ID:Subject:Cc:To:Sender:From:Date:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=q/6Zc0pbDfC9dsBSDo9+oO1LskHbllfR6MQNap0nd0g=; b=LFRf8AYa28+FHy/MFbjtVlCeaQ ZZ7DA0tuWRoU2tVAo5QgdnUFii74bRHwzTz66A8CzxQ3gM+wZcHGwJurNpyT8Jcs4ccTgyjKQjPUv QAcYrhxC1sgDDJZXc7Um+XsnaHKVY3V2tSJMXW9tT5yc4Q+mRDHJd5fFHVXZKBhxrZUk=; Received: from depesz by depesz.com with local (Exim 4.94.2) (envelope-from ) id 1oitei-0085Xf-1Q; Thu, 13 Oct 2022 10:33:28 +0200 Date: Thu, 13 Oct 2022 10:33:28 +0200 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: Sengottaiyan T Cc: MichaelDBA , pgsql-performance@postgresql.org Subject: Re: Identify root-cause for intermittent spikes Message-ID: Reply-To: depesz@depesz.com References: <0e34d222-d3b8-02fc-f60a-0487212e0cd4@sqlexec.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Oct 12, 2022 at 10:46:23PM +0530, Sengottaiyan T wrote: > Thanks, Michael. > > Due to reactive nature of the intermittent alerts, Is there any table which > stores the historical information / periodic snapshots captured from the > pg_stat_activity view? No. Unless you will make one, and add data to it from some cron-like thing. Best regards, depesz