#28062: Using QuerySet.iterator() with pgBouncer leads to nonexistent cursor
errors
-------------------------------------+-------------------------------------
Reporter: Sergey Fursov | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Release blocker | 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 Florian Apolloner):
Replying to [comment:2 Josh Smeaton]:
> - We could also add an argument to .iterator() that allows users to opt-
in to the new server side cursors. We'd need to document the limitations,
and suggest ideal scenarios (use transaction.atomic, or
.using('non_pgbouncer_transaction_connection')).
Opting in seems like a reasonable thing to do, though given the fact that
it will generally not work for anyone using pgbouncer in a specific mode,
it might make more sense if we'd also provide a switch to turn this off/on
globally (database options).
--
Ticket URL: <https://code.djangoproject.com/ticket/28062#comment:6>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.53824f0f5ef9ff16204049243d25e8f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
