Sep 21 • 🐳 Self-hosting
What is actually eating your n8n disk?
Pruning being on does not stop the disk filling.
n8n prunes on age OR count, whichever comes first. The defaults keep 10,000 executions or 14 days of them. Executions stuck in waiting never prune at all, and anything you tagged in the UI never prunes either.
Then Postgres does not hand the space back when the rows finally go. Deleting them does not move df -h.
Run this against your n8n database and paste what comes back:
SELECT relname AS table_name, pg_size_pretty(pg_total_relation_size(c.oid)) AS total_size FROM pg_class c JOIN pg_namespace n ON n.oid = c.relnamespace WHERE n.nspname = 'public' AND c.relkind = 'r' ORDER BY pg_total_relation_size(c.oid) DESC LIMIT 5;
I want to see what is actually at the top for people. Curious whether execution_data wins every time or whether something else turns up.
0
0 comments
What is actually eating your n8n disk?
skool.com/houseofloops
Run your own AI infrastructure — Docker, homelab, local LLMs, n8n. The stack underneath the automation, and answers when it breaks.
Powered by