Thread: OFFSET and subselects
I recently noticed a behaviour which seems quite suboptimal - I am working on a "mart" type application, which in practice means I end up with queries which have a few filters on several central tables, and then a few dozen subselects for other info (which seems to perform better than several dozen equivalent LEFT JOINs do). I am running in trouble with pagination here, somehow (rather naively) I assumed that when doing a LIMIT and OFFSET, the subselects on the records before the OFFSET would not be performed, which quite apparently is not the case. So, LIMIT 50 OFFSET 0 takes 100ms to run, LIMIT 50 OFFSET 50 takes 200ms, LIMIT 50 OFFSET 100 takes 300ms; and so forth, this really becomes unacceptable after a few pages. I was wondering how I migh improve the situation? Two possibilities come to mind: a) run the query without the subselects and store the LIMIT 50 in a temp table, doing a select all from that with the subselects as a separate query or b) similar, but run the queries from the subselects as separate queries, assembling everything in the app. Is one better than the other in any way? Are there better ways to deal with this? Thanks
dbichko@genpathpharma.com (Dmitri Bichko) writes: > I am running in trouble with pagination here, somehow (rather naively) I > assumed that when doing a LIMIT and OFFSET, the subselects on the records > before the OFFSET would not be performed, which quite apparently is not the > case. So, LIMIT 50 OFFSET 0 takes 100ms to run, LIMIT 50 OFFSET 50 takes > 200ms, LIMIT 50 OFFSET 100 takes 300ms; and so forth, this really becomes > unacceptable after a few pages. If you don't need any of the results of the subqueries in your WHERE clause then you can do this by introducing a view in your query like: SELECT *, (SELECT ...) AS sub_1, (SELECT ...) AS sub_2, (SELECT ...) AS sub_3 FROM ( SELECT x,y,z FROM ... WHERE ... )LIMIT 50 OFFSET 50 If you do use the results of the subqueries in your where clause or order by clause then, well, you're SOL. Since the OFFSET and LIMIT clauses only kick in after the where clause restrictions are taken into account. -- greg