| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Igor Neyman <ineyman(at)perceptron(dot)com>, "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 17:31:52 |
| Message-ID: | 57321B08.9040607@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 05/10/2016 09:50 AM, Igor Neyman wrote:
> 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.
>
You could use iotop to determine which postgres pid is eating the IO,
then use statement logging with PID (or pg_stat_activity/statement) to
see what the system is actually doing.
JD
> Regards,
>
> Igor Neyman
>
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melvin Davidson | 2016-05-10 18:01:16 | Re: Increased I/O / Writes |
| Previous Message | Igor Neyman | 2016-05-10 16:50:04 | Re: Increased I/O / Writes |