It turned out that the easiest and most effective way to handle it was
to run this script at an off peak time:
http://djangosnippets.org/snippets/1273/
Not really sure how long it actually took to ran (I should have timed
it...), but it was less than 2 and a half hours on 40+ million
records.
When I attempt to run a normal cleanup, the cleanup eventually loses
connection to the database and dies. I think I am going to have to
take the manual approach.
One thing that I wanted to point out is that I think you meant the SQL
equivalent is:
DELETE FROM django_session WHERE expire_date <
On 8/20/2010 9:44 PM, Russell Keith-Magee wrote:
> On Fri, Aug 20, 2010 at 11:51 PM, bfrederi wrote:
>> I just wanted to know if anyone had an opinion or whether running a
>> django-admin.py cleanup on 40 million session rows might slow down or
>> lock up the database. I
On Fri, Aug 20, 2010 at 11:51 PM, bfrederi wrote:
> I just wanted to know if anyone had an opinion or whether running a
> django-admin.py cleanup on 40 million session rows might slow down or
> lock up the database. I would like to do this cleanup ASAP, but I was
>
I just wanted to know if anyone had an opinion or whether running a
django-admin.py cleanup on 40 million session rows might slow down or
lock up the database. I would like to do this cleanup ASAP, but I was
concerned it might cause some issues.
--
You received this message because you are
5 matches
Mail list logo