self-hosted
self-hosted copied to clipboard
Large repack.log_* toast_size in pg_class
Self-Hosted Version
23.3.1
CPU Architecture
x86_64
Docker Version
25.0.4-1.el7
Docker Compose Version
1.29.2
Steps to Reproduce
Our self hosted Sentry instance ran out of disk today. I followed documented steps to reduce the size of the nodestore table, and reclaimed 50GB of disk, but noticed in the pg_class table 2 very large toast sizes below:
SELECT oid::regclass, reltoastrelid::regclass, pg_relation_size(reltoastrelid) AS toast_size FROM pg_class WHERE relkind = 'r' AND reltoastrelid <> 0 ORDER BY 3 DESC;
oid | reltoastrelid | toast_size
--------------------------------------------+------------------------------+--------------
repack.log_20249 | pg_toast.pg_toast_1181849834 | 157098164224
repack.log_1181849834 | pg_toast.pg_toast_2923418714 | 12328960
What are these tables, and are the safe to remove?
Expected Result
I'd like an understanding of these undocumented tables
Actual Result
Tables are consuming a lot of disk for an unknown reason
Event ID
No response