directly against the`audit_logs` table in the database. We advise users to only purge old records (>1yr)

and in accordance with your compliance requirements.

You may choose to run a`VACUUM` or`VACUUM FULL` operation on the audit logs table to reclaim disk space. If you choose to run the`FULL` operation, consider the following when doing so:

-**Run during a planned mainteance window** to ensure ample time for the operation to complete and minimize impact to users

-**Stop all running instances of`coderd`** to prevent connection errors while the table is locked. The actual steps for this will depend on your particular deployment setup. For example, if your`coderd` deployment is running on Kubernetes:

kubectl scale deployment coder --replicas=0 -n coder

-**Terminate lingering connections** before running the`VACUUM` operation to ensure it starts immediately

SELECT pg_terminate_backend(pg_stat_activity.pid)

FROM pg_stat_activity

WHEREpg_stat_activity.datname='coder'AND pid<> pg_backend_pid();

-**Only`coderd` needs to scale down** - external provisioner daemons, workspace proxies, and workspace agents don't connect to the database directly.

After the vacuum completes, scale coderd back up:

kubectl scale deployment coder --replicas= -n coder

Consider exporting or archiving these records before deletion: