On 01/09/16 17:56, Mark Kirkwood wrote:
the other way to attack this is to trace your backend postgres
process (err perfmon...no idea how to do this on windows...)
No idea why I thought you were on windows (maybe was reading another
message just before yours) - sorry!
--
Sent via
On 01/09/16 10:01, Bobby Mozumder wrote:
Is it possible to find the number of disk IOs performed for a query? EXPLAIN
ANALYZE looks like it shows number of sequential rows scanned, but not number
of IOs.
My database is on an NVMe SSD, and am trying to cut microseconds of disk IO per
query
On Wed, Aug 31, 2016 at 3:01 PM, Bobby Mozumder wrote:
> Is it possible to find the number of disk IOs performed for a query?
> EXPLAIN ANALYZE looks like it shows number of sequential rows scanned, but
> not number of IOs.
>
> My database is on an NVMe SSD, and am trying to
On Aug 31, 2016, at 3:01 PM, Bobby Mozumder wrote:
>
> Is it possible to find the number of disk IOs performed for a query? EXPLAIN
> ANALYZE looks like it shows number of sequential rows scanned, but not number
> of IOs.
Postgres knows the number of rows it will need
Is it possible to find the number of disk IOs performed for a query? EXPLAIN
ANALYZE looks like it shows number of sequential rows scanned, but not number
of IOs.
My database is on an NVMe SSD, and am trying to cut microseconds of disk IO per
query by possibly denormalizing.
Thank you,