Postgres is growing rapidly - Manual cleanup

[untitaker]

@chrisvdb Please refer to

Postgres nodestore_node table 124gb

To answer the question about purpose of nodestore: nodestore stores the raw, unindexed parts of the data of an event. For example all event breadcrumbs and contexts are stored there. Clickhouse only stores the data you can search and aggregate by. It only has indices, so to speak. nodestore has multiple backends. On sentry.io it is not postgres, but google bigtable. We use the postgres backend for local development and for onpremise, but for large-scale installations it is suboptimal. We don’…

Nodestore_node size

There are already multiple threads about nodestore disk usage, please use those.

Question: What data stored in nodestore_node table?

I have on-premise install (version 10.0.0), and this node not used currently No teams / No projects / No one send data to this instance But Table / Size / External Size nodestore_node / 319 GB / 316 GB This instance installed ~100 days ago

Postgres DB growth

Hi. We’re using version 20.7.2. And we faced a situation, when postgres database grows infinitely. Cleanup cron set up to start every 24h and SENTRY_EVENT_RETENTION_DAYS=30, but nodestore_node table size keeps growing and growing, about 9Gb a day. Here’s nodestore_node table size comparing with the others, and volume sizes of another services. table_schema | table_name | row_estimate | total | index | toast | table --------------------+---…

or any search on “postgres” or “nodestore”.

However, if the files are actually created by systemd-coredump (as described @lukas ) I believe your database may be crashing regularly?