Timeline for How to accurately measure query time in PostgreSQL (because EXPLAIN ANALYZE does not seem to do it)?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2020 at 22:23 | history | edited | CommunityBot |
added [query-performance] to 2412 questions - Shog9 (Id=1924)
|
|
| Sep 20, 2019 at 11:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 12, 2019 at 17:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 12, 2019 at 1:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 5, 2018 at 22:11 | comment | added | B Seven | So, it takes 100ms to execute the query, and 2,000ms to send the result over the network...that makes more sense. | |
| Jul 5, 2018 at 21:50 | answer | added | jjanes | timeline score: 0 | |
| Jul 5, 2018 at 21:13 | answer | added | Evan Carroll | timeline score: 1 | |
| Jul 5, 2018 at 18:20 | comment | added | user1822 |
The time reported by explain (analyze) indeed does not include the time it takes to send the data to the SQL client. It is the time the server needed to completely prepare the result so that it could be sent to the driver. As any delay after that is completely up to the combination of the SQL client and the network between client & server it's impossible for explain to show that
|
|
| Jul 5, 2018 at 17:58 | history | asked | B Seven | CC BY-SA 4.0 |