#30533: Delete cascade can break postgresql database: too large 'DELETE FROM a
WHERE a.b_id IN (...)'
-------------------------------------+-------------------------------------
Reporter: Thomas Riccardi | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: queryset delete | Triage Stage:
cascade batch bulk_batch_size | Unreviewed
postgresql crash |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* version: 2.0 => master
Comment:
Thanks for the report. Do you know any source that describes the max
number of parameters for PostgreSQL? (e.g. 64k is specified in db docs on
Oracle).
--
Ticket URL: <https://code.djangoproject.com/ticket/30533#comment:1>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.bff0a711c53ad38bac5ec33ea85d7255%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
