[ckan-dev] How to reduce the size of the database "activity" table?

[Ian Ward]

We should have a CLI command and background job for removing old activity
entries, or collapsing them to 1/day/week/month per dataset.

An option to disable activities entirely would be great for some sites too.

Until we have features like that it should be safe to remove old activity
records directly from the database. I recommend backing up your DB before
any direct modifications, of course.

On Tue, Nov 13, 2018 at 2:39 PM Brian Bonnlander <bonnland at ucar.edu> wrote:

>
> Hi CKAN developers,
>
> We have a CKAN instance with datasets whose metadata are continually
> being updated using the CKAN harvester.
>
> Only one field is typically changed:  the time range for the data (more
> data gets added every few days).
>
>
> After running for more than a year, we now have an "activity" table with
> over 200,000 rows, and the database has grown to around 10 GB in size.
>
> Is there a way to safely clear the "activity" table?   Or maybe keep it
> from growing in the first place, since the changes being recorded are
> not that interesting in the first place?
>
>
> Thank you for your time,
>
> --Brian
>
>
> -------
>
> Brian Bonnlander
>
> National Center for Atmospheric Research
>
> Boulder, Colorado  USA
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20181113/97fba6a7/attachment-0002.html>