From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
---|---|
To: | "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Increased I/O / Writes |
Date: | 2016-05-10 16:50:04 |
Message-ID: | DM2PR07MB5576EE4A736CD2F0E6692A2DA710@DM2PR07MB557.namprd07.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of drum(dot)lucas(at)gmail(dot)com
Sent: Sunday, May 08, 2016 10:07 PM
To: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: [GENERAL] Increased I/O / Writes
Hi all,
I've recently an increase IO for writes on my DB. I'm currently using PostgreSQL 9.2.
[Inline images 1]
I know that much improvements can be done (as I'm using SATA disks), but my question is:
Is there a way to detect the queries that are causing that?
I can use pg_stat_statements to get the most usage queries, but I was wondering how can I find the queries that are causing that much IO?
Please, if anyone can share anything.. Thanks a lot!
Lucas
So, what’s wrong with using pg_stat_statements?
It has a set of columns pertaining to IO.
Regards,
Igor Neyman
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2016-05-10 17:31:52 | Re: Increased I/O / Writes |
Previous Message | John McKown | 2016-05-10 16:43:53 | Re: Postgres RFC3339 datetime formatting |