Timeline for PostGIS & Pagination
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 23, 2020 at 14:42 | vote | accept | Thomas Coquet | ||
| Sep 23, 2020 at 14:37 | history | edited | geozelot |
edited tags
|
|
| Sep 23, 2020 at 14:25 | answer | added | geozelot | timeline score: 4 | |
| Sep 23, 2020 at 14:22 | comment | added | JGH |
see this post. It contains ordering by id+0 or to add an offset 0 to prevent the default index from being used
|
|
| Sep 23, 2020 at 14:19 | comment | added | Thomas Coquet |
It uses an index scan on the id but the spatial index does not kick in, hence the query is more than 10x slower.
|
|
| Sep 23, 2020 at 14:09 | comment | added | JGH |
what is wrong with the standard solution? (select id ... where id > lastMaxID order by id limit 100) You would have to run the spatial query for each page anyways.
|
|
| Sep 23, 2020 at 13:45 | comment | added | Thomas Coquet | My previous question was about a weird performance w.r.t. the area of a geometry that I solved using EXPLAIN ANALYZE. Here I am asking more generally about implementing constant time pagination with spatial indexes (like keyset pagination). I can rewrite the previous one if you think that's better. | |
| Sep 23, 2020 at 13:17 | comment | added | jgm_GIS | This is essentially the same question the poster made a few days ago. See gis.stackexchange.com/questions/374461/… | |
| Sep 23, 2020 at 13:03 | history | asked | Thomas Coquet | CC BY-SA 4.0 |