#19918: select_for_update runs on db_for_read rather than db_for_write
-------------------------------------+-------------------------------------
Reporter: | Owner: kux
alexandruioan.cucu@… | Status: assigned
Type: Bug | Version: master
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by anonymous):
The fact that the db was running with --read-only flag is a fortunate
case. Otherwise this bug would cause subtle concurrency issues since all
exclusive locks would be held on the slave db instead of master.
--
Ticket URL: <https://code.djangoproject.com/ticket/19918#comment:7>
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/086.949587ff20331cfe1ca52e9dfc375025%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
