MIME-Version: 1.0
References: <CAA23SdsOB8RSGAXHH-f1pZ76EaWNuSy2FUvmaBqVSaPJqzi1FQ@mail.gmail.com>
In-Reply-To: <CAA23SdsOB8RSGAXHH-f1pZ76EaWNuSy2FUvmaBqVSaPJqzi1FQ@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Fri, 17 May 2024 13:23:09 -0400
Message-ID: <CAKAnmmLUNqcdt=koFQD9PBRRX5Q=8VCFXpV47oNN1fJdfkYzKQ@mail.gmail.com>
Subject: Re: Execution history of a single query
To: arun chirappurath <arunsnmimt@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000002115a40618a99dfd"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmLUNqcdt%3DkoFQD9PBRRX5Q%3D8VCFXpV47oNN1fJdfkYzKQ%40mail.gmail.com>
Precedence: bulk

--0000000000002115a40618a99dfd
Content-Type: text/plain; charset="UTF-8"

Not directly through pg_stat_statements, no. But you can:

* Use log_min_duration_statement to spy on individual runs
* Periodically copy pg_stat_statements to another table, reset the stats,
and then you have some time-based buckets to play with.

Cheers,
Greg

--0000000000002115a40618a99dfd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Not directly through pg_stat_statements, no. But you can:<=
div><br></div><div>* Use log_min_duration_statement to spy on individual ru=
ns</div><div>* Periodically copy pg_stat_statements to another table, reset=
 the stats, and then you have some time-based buckets to play with.</div><d=
iv><div><div><br></div><div>Cheers,</div><div>Greg</div><div><br></div></di=
v></div></div>

--0000000000002115a40618a99dfd--