#34597: Queryset (split) exclude's usage of Exists is significantly slower than
subquery
-------------------------------------+-------------------------------------
Reporter: Lorand Varga | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Had
[https://old.reddit.com/r/PostgreSQL/comments/1am2e8x/whats_new_in_the_postgres_16_query_planner/
a discussion with Postgres major contributor about this very issue] and
[https://techcommunity.microsoft.com/t5/azure-database-for-
postgresql/what-s-new-in-the-postgres-16-query-planner-
optimizer/ba-p/4051828#right-anti-join a query planer optimization in
Postgres 16+] that might make the `EXISTS` solution worth investigating.
--
Ticket URL: <https://code.djangoproject.com/ticket/34597#comment:14>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d8bd9ff87-fac21f0c-2302-489e-9982-7fdc18e5fac4-000000%40eu-central-1.amazonses.com.
