#9964: Transaction middleware closes the transaction only when it's marked as
dirty
---------------------------------------------------+------------------------
Reporter: ishirav | Owner:
mtredinnick
Status: assigned | Milestone: 1.3
Component: Database layer (models, ORM) | Version: 1.0-beta-1
Resolution: | Keywords:
transactions
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by Tuxie):
I'm not a Django user but I am a PostgreSQL DBA and I must say that I'm
fascinated by how you have handled this bug. Still open after 11 months
because people are actually defending leaving dangling transactions? Just
wow!
These dangling transactions will prevent the autovacuum daemon from doing
its job, writes will slow to a crawl after a while and tables will just
grow and grow, never being able to reuse the disk space after previous
deletes and updates.
Always COMMIT, ROLLBACK or disconnect after starting a transaction or
never open the transaction in the first place. The current behaviour is
not an optimization, it has serious performance implications for apps with
any amount of regular writes, so bad it practically makes
Django+PostgreSQL unusable for any long running dynamic applications of
non-trivial size.
--
Ticket URL: <http://code.djangoproject.com/ticket/9964#comment:34>
Django <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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
