#7760: Queries on large primary tables with limit/offset clauses are slow
---------------------------------------------+------------------------------
Reporter: henrybaxter | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: SVN
Resolution: | Keywords:
database,admin,slow,query
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* stage: Unreviewed => Design decision needed
* needs_tests: => 0
* needs_docs: => 0
Comment:
At the moment, I suspect this is just not worth it, since there are so
many cases where it's not going to be a useful transform and it's a whole
separate code path to have to maintain. If it's a real performance issue
for a particular use-case, then the correct solution is "don't do that".
Doing limits and offsets is already a performance hit. Doing a slightly
better related filter and/or using `values()` is going to be the solution
in most cases.
Leaving open for a bit because I don't want to make a rush judgement, but
I'm uninspired about the proposal at the moment.
--
Ticket URL: <http://code.djangoproject.com/ticket/7760#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
