| From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
|---|---|
| To: | "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Increased I/O / Writes |
| Date: | 2016-05-11 01:15:23 |
| Message-ID: | CAL_0b1uWWExXeTRL=rA43mLkJKomcHZK24Bo+0x=K1=c50eh6Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, May 8, 2016 at 7:07 PM, drum(dot)lucas(at)gmail(dot)com
<drum(dot)lucas(at)gmail(dot)com> wrote:
> 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?
Take a look at this tool:
https://github.com/grayhemp/pgcookbook/blob/master/statement_statistics_collecting_and_reporting.md
--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA
http://www.linkedin.com/in/grayhemp
https://github.com/grayhemp
+1 (415) 867-9984, +7 (499) 346-7196, +7 (988) 888-1979
gray(dot)ru(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | fredrik | 2016-05-11 04:31:14 | Streaming replication, master recycling |
| Previous Message | Lucas Possamai | 2016-05-10 21:54:55 | Re: Unused indexes - PostgreSQL 9.2 |