On Tue, May 10, 2016 at 1:31 PM, Joshua D. Drake <jd@xxxxxxxxxxxxxxxxx> wrote:
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.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
I highly recommend you look into using PgBadger. It gives you a great deal of info about your queries, including I/O, above and beyond pg_stats.
PgBadger info PgBadger download
--
Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.![]()
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
