Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Facebook
Downloads
Home
>
mailing lists
Explain analyse with track_io_timing - Mailing list pgsql-performance
From
Jayadevan M
Subject
Explain analyse with track_io_timing
Date
March 10, 2022
05:10:17
Msg-id
CAFS1N4j=QMEsQgnb4ZLjoAgZNwaK-aNkL8y9EBvFVV2PS=dZ8w@mail.gmail.com
Whole thread
Raw
Responses
Re: Explain analyse with track_io_timing
List
pgsql-performance
Tree view
Hello team,
What is the unit of I/O Timings in explain (analyze, buffers) ? There is a plan with quite a few nodes. In each case, the value of I/O Timings is much more than the time for the outer node. A few lines from the plan -
Hash Left Join (cost=14320945.22..7099974624.27 rows=194335062701 width=5511) (actual time=107913.021..
108109
.313 rows=759 loops=1)
Buffers: shared hit=738871 read=1549646, temp read=92710 written=92973
I/O Timings: read=
228324
.357
-> Hash Left Join (cost=14049069.69..246411189.41 rows=18342148438 width=5467) (actual time=96579.630..
96774
.534 rows=759 loops=1)
Buffers: shared hit=684314 read=1377851, temp read=92710 written=92973
I/O Timings: read=
217899
.233
At the end, there is
Execution Time: 108117.006 ms
So it takes about 108 seconds. But the I/O Timings are higher.
Best Regards,
Jay
pgsql-performance
by date:
Previous
From:
aditya desai
Date:
09 March 2022, 06:09:55
Subject:
Re: Any way to speed up INSERT INTO
Next
From:
Julien Rouhaud
Date:
10 March 2022, 06:05:28
Subject:
Re: Explain analyse with track_io_timing
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
I confirm that I have read and accepted PostgresPro’s
Privacy Policy
.
I agree to get Postgres Pro discount offers and other marketing communications.
✖
×
×
Everywhere
Documentation
Mailing list
List:
all lists
pgsql-general
pgsql-hackers
buildfarm-members
pgadmin-hackers
pgadmin-support
pgsql-admin
pgsql-advocacy
pgsql-announce
pgsql-benchmarks
pgsql-bugs
pgsql-chat
pgsql-cluster-hackers
pgsql-committers
pgsql-cygwin
pgsql-docs
pgsql-hackers-pitr
pgsql-hackers-win32
pgsql-interfaces
pgsql-jdbc
pgsql-jobs
pgsql-novice
pgsql-odbc
pgsql-patches
pgsql-performance
pgsql-php
pgsql-pkg-debian
pgsql-pkg-yum
pgsql-ports
pgsql-rrreviewers
pgsql-ru-general
pgsql-sql
pgsql-students
pgsql-testers
pgsql-translators
pgsql-www
psycopg
Period
anytime
within last day
within last week
within last month
within last 6 months
within last year
Sort by
date
reverse date
rank
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
By continuing to browse this website, you agree to the use of cookies. Go to
Privacy Policy
.
I accept cookies