#29760: Cursors are being closed explicitly in autocommit mode
-------------------------------------+-------------------------------------
Reporter: Ali Teoman Unay | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
Keywords: cursor, sql, | Triage Stage: Accepted
database, autocommit, |
transactions, postrgresql, |
psycopg |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
For the record the above comment was related to the use of `pg_bouncer`
which is documented to be causing issue with `iterator()`.
> I believe it appears when the cursor is destroyed before the transaction
ended and it points to a synchronization error which might be related to
this issue.
Ali, I'm not sure I'm following along here. The ticket mentions autocommit
but you're a mentioning transactions here. Do you happen to use connection
polling as well?
--
Ticket URL: <https://code.djangoproject.com/ticket/29760#comment:10>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.1a89fc887316d9cade9c0dbbfc305b2a%40djangoproject.com.
