Not really. What's much faster is the wraparound protection vacuum which is a sp... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		pilif on April 5, 2016 \| parent \| context \| favorite \| on: PostgreSQL Bloat: origins, monitoring and managing Not really. What's much faster is the wraparound protection vacuum which is a special more thorough vacuum that runs at a configured interval which defaults to every 200M transactions against a database. Only that one is sped up to now run roughly at the same speed as the normal vacuum

arthursilva on April 5, 2016 [–]

It looked to me that the freeze map allowed vacuum to skip pages not touched since last run, so avoiding a lot of work between runs.

anarazel on April 5, 2016 | [–]

That's not new though - the visibility map has done so for years (8.4 IIRC).

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact