Timeline for Optimizing a simple query joining two big tables
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2020 at 22:25 | history | edited | CommunityBot |
added [postgresql-performance] to 571 questions - Shog9 (Id=1924)
|
|
| Jan 7, 2020 at 22:23 | history | edited | CommunityBot |
added [query-performance] to 2412 questions - Shog9 (Id=1924)
|
|
| Aug 2, 2018 at 12:48 | comment | added | Erwin Brandstetter | So do you have your answer? | |
| Jun 7, 2018 at 12:35 | history | edited | Erwin Brandstetter | CC BY-SA 4.0 |
add info from comment, minor edits
|
| Jun 6, 2018 at 13:59 | history | edited | Erwin Brandstetter | CC BY-SA 4.0 |
add tags, format, sharpen title, minor edits
|
| Jun 6, 2018 at 13:53 | answer | added | Erwin Brandstetter | timeline score: 4 | |
| Jun 6, 2018 at 12:53 | comment | added | user1822 | The query takes less than a second to run (888 milliseconds) - if you are seeing "4 mintues" somewhere the difference is due to the way the rows are transferred and displayed in whatever application you use. | |
| Jun 6, 2018 at 10:59 | answer | added | user126897 | timeline score: 0 | |
| Jun 6, 2018 at 10:52 | history | edited | Darth Kangooroo | CC BY-SA 4.0 |
Replaced the result of EXPLAIN by the result of EXPLAIN ANALYZE
|
| Jun 6, 2018 at 10:23 | history | asked | Darth Kangooroo | CC BY-SA 4.0 |