Timeline for Postgres optimizing nested exists
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 9, 2017 at 0:38 | comment | added | user3747260 | I just tried the indexed query. It sounds promising, but unfortunately a sequential scan was still used. I'll play around with it some more though. As for the number of events, 189 is the id of a foreign key so there are many rows in the event table that have that value. Sorry if that wasn't clear. | |
| Jan 8, 2017 at 22:53 | comment | added | Evan Carroll | my bad, I was eating glue. | |
| Jan 8, 2017 at 22:49 | history | edited | Evan Carroll | CC BY-SA 3.0 |
deleted 108 characters in body
|
| Jan 8, 2017 at 22:49 | review | Low quality posts | |||
| Jan 9, 2017 at 0:36 | |||||
| Jan 8, 2017 at 22:47 | comment | added | ypercubeᵀᴹ |
event_2. tickrange <@ event_1. newrange
|
|
| Jan 8, 2017 at 22:46 | comment | added | Evan Carroll |
@TypoCubeᵀᴹ where do you see any comparison to anything that doesn't have the +500? Am I missing something doesn't the CTE event shadow all future references to event?
|
|
| Jan 8, 2017 at 22:44 | comment | added | ypercubeᵀᴹ |
They don't compare [x1,y1+500] @> [x2,y2+500]. They compare [x1,y1+500] @> [x2,y2]
|
|
| Jan 8, 2017 at 22:31 | history | answered | Evan Carroll | CC BY-SA 3.0 |