pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: hubert depesz lubaczewski <depesz@depesz.com>
To: Sengottaiyan T <techsenko@gmail.com>
Cc: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Identify root-cause for intermittent spikes
Date: Thu, 13 Oct 2022 10:33:28 +0200
Message-ID: <Y0fNWMPTIbrC+Mwy@depesz.com> (raw)
In-Reply-To: <CADjQTvLaCZZJ0juFgShSZWKi2+04s5qhwzMmwjMYHRU5akwZHA@mail.gmail.com>
References: <CADjQTv+_MbRhM6SHmsK9fr7deWdrKe9Y66QCBdFoFT0vhK+RJA@mail.gmail.com>
	<CADjQTvLARNBi0zSSAXFyQJdd8+o0tSX2mPfdAOA9rcNfhD5Axw@mail.gmail.com>
	<0e34d222-d3b8-02fc-f60a-0487212e0cd4@sqlexec.com>
	<CADjQTvLaCZZJ0juFgShSZWKi2+04s5qhwzMmwjMYHRU5akwZHA@mail.gmail.com>

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

view thread (10+ messages)  latest in thread

Message-ID: <Y0fNWMPTIbrC+Mwy@depesz.com>
Permalink:  ../Y0fNWMPTIbrC+Mwy@depesz.com/
Also on:    postgresql.org/message-id/Y0fNWMPTIbrC+Mwy@depesz.com

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: depesz@depesz.com, techsenko@gmail.com, MichaelDBA@sqlexec.com
  Subject: Re: Identify root-cause for intermittent spikes
  In-Reply-To: <Y0fNWMPTIbrC+Mwy@depesz.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox