Timeline for Same postgres query in two different instances with the same data but with different times
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 17 at 9:04 | 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. | |
| Oct 16 at 23:29 | history | edited | Erwin Brandstetter | CC BY-SA 4.0 |
denoise
|
| Oct 16 at 23:28 | comment | added | Erwin Brandstetter |
Postgres execution times are 14.87 ms / 776.976 ms. The huge rest of 40s / 400s is outside of Postgres' jurisdiction. Also, Postgres 11 has reached EOL in 2023. Use a current version for your tests. Either way, a multicolumn index on ("SignalSettingId", "DateTime") should help (but not much for the given filter values).
|
|
| Oct 16 at 22:03 | 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. | |
| Jun 14 at 15:03 | 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. | |
| Feb 2 at 20:08 | 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. | |
| Sep 22, 2023 at 8:06 | 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 23, 2023 at 0:07 | 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 19, 2023 at 23: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. | |
| Sep 14, 2022 at 13:04 | 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 16, 2022 at 21:07 | 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. | |
| Feb 25, 2021 at 16:05 | comment | added | Igor Gois | @bobflux, yes. the query is: EXPLAIN (FORMAT JSON, ANALYZE, BUFFERS) SELECT "Id", "DateTime", "SignalRegisterId", "Raw" FROM "SignalRecordsBlobs" WHERE "SignalSettingId" = 103 AND "DateTime" BETWEEN '2019-11-28T14:00:12.540200000' AND '2020-07-23T21:12:32.249000000'; | |
| Feb 24, 2021 at 16:03 | comment | added | bobflux | Besides the configuration issue, row estimates are wrong in one of the queries. Did you run ANALYZE? | |
| Feb 23, 2021 at 21:15 | history | edited | user212533 |
Added Postgres version
|
|
| Feb 23, 2021 at 20:59 | answer | added | Burak Yurdakul | timeline score: 0 | |
| Feb 23, 2021 at 19:47 | review | First posts | |||
| Feb 23, 2021 at 21:15 | |||||
| Feb 23, 2021 at 19:41 | history | asked | Igor Gois | CC BY-SA 4.0 |