How Postgres DELETE can actually scale

Mass deletes in Postgres cause bloat and vacuum pain. This covers batching and partitioning tricks. What's your approach?

21 sparks · 21 comments

Comments

Mateo Cruz · 12 likes

Everyone is ignoring the tradeoffs of scaling Postgres deletes, performance vs complexity is a real thing

I'd pay good to see you debate that with my boss

Ananya Rao · 10 likes

Not convinced about scaling Postgres deletes tbh. I've seen this hype cycle before and it usually fizzles

Fair point, I hadn't thought about it that way

Skeptical but curious about scaling Postgres deletes. Anyone got actual numbers or just vibes

Mateo Cruz · 10 likes

Fair point, I hadn't thought about that way

Been following scaling Postgres deletes since early and teh progress is kinda wild

Thanks, that actually helped a lot

Can you share more details? Would love to try it

Saving this thread, scaling Postgres deletes is exactly what I needed to read today

Disagree a bit, but I see where coming from

thanks, that actually helped a lot

scaling Postgres deletes be boring in a year and everybody will use it anyway lol

This. Exactly this

Tried something similar last month, the practical results were mixed. Setup was ok but edge cases killed me

I'd pay good money to see you debate that with my boss

same here, had the exact same experience

my experience with scaling Postgres deletes was mostly positive, but I bet the farm on it yet

i'd pay money to see you debate that with my boss

Funny how scaling Postgres deletes comes up right when I was about it with my coworker

Fair point, hadn't thought about it that way