| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Mikael Carneholm <Mikael(dot)Carneholm(at)WirelessCar(dot)com> |
| Cc: | "'Pgsql-General (E-mail)" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Queries causing highest I/O load since pg_stat_reset? |
| Date: | 2005-11-14 22:56:08 |
| Message-ID: | 20051114225608.GS18570@pervasive.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I don't think there's any way to do this currently. Maybe if you wrote
an external program that polled pg_stat_activity and then correlated
procpid to the output of top, etc.
On Mon, Nov 14, 2005 at 08:59:19PM +0100, Mikael Carneholm wrote:
> Hi,
>
> is it possible to retrieve a list of queries that has caused the highest i/o load? Something like
>
> (1) select pg_stat_reset();
> (2) run some queries for a while
> (3) list the queries that caused the highest i/o since step (1)
>
> ?
>
> /Mikael
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mikael Carneholm | 2005-11-14 23:06:13 | Re: Updated: partitioning functions |
| Previous Message | Jim C. Nasby | 2005-11-14 22:54:41 | Re: 3 x PostgreSQL in cluster/redunant |