Burak Yigit Kaya

@Kriechi well here's the break down (I think it is mostly `h2`'s fault btw which you are also a maintainer of): 1. `h2` uses a single `hpack.Encoder` and `hpack.Decoder` instance...

There are a few interesting and important things: 1. We can never add the `VACUUM FULL public.nodestore_node;` part in any kind of production setup as it will lock the whole...

The consensus is towards an filesystem-based backend right now. Since the current FS-backed node store implementation is a bit naive and geared towards debuggability, it will take some more time...

@manishrawat1992 can you explain what you mean by "leakage"?

@manishrawat1992 the main issue was not fragmentation as far as I'm aware. The main issue with Postgres is even if you delete the rows, the disk space is not given...

I'd still be wary of using a Postgres table for this as it will still be a very volatile table needing a vacuum eventually. I think sqlite would be a...

@LordSimal there's nothing wrong with the clean up. It fully aligns what is documented over at https://develop.sentry.dev/self-hosted/troubleshooting/postgres/ -- Note the bold text higlighting that the disk usage spiking before going...

Closing due to inactivity. @staticshock feel free to re-open or comment if you still need something from us here.

Hi @boxed and thank you so much for opening this issue (and your interest in Spotlight)! We are well aware that the landing page and even some other pages on...

And to answer your question briefly: Spotlight is a fully local debugging tool that surfaces events from Sentry SDKs in your applications for errors with neat stack traces, performance characteristics,...