heat/heat/db
Crag Wolfe 882a640f18 Refactor purge_deleted, operate on batches of stacks
Avoid large sql "in" clauses by operating on smaller batches of stacks
at a time.

To avoid transaction overhead and contention on the resource table,
the first deletions occur outside of a transaction (are
autocommitted). This is OK because the purge is re-rentrant -- we
won't lose any stack_id's to delete if something goes wrong before the
conn.begin() block. That is, we will not orphan any rows if the purge
is run multiple times where an error occurs.

Change-Id: I9edf0558ed54820842193560e323df6501411d1d
2016-11-28 20:13:35 -08:00
..
sqlalchemy Refactor purge_deleted, operate on batches of stacks 2016-11-28 20:13:35 -08:00
__init__.py Do not initialize anything during import phase 2013-04-24 10:03:06 -07:00
api.py Don't always eagerly load the raw_template for a stack 2016-10-04 08:25:01 -04:00
utils.py Refactor purge_deleted, operate on batches of stacks 2016-11-28 20:13:35 -08:00