Re: Lock-free compaction. Why not?
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Ahmed Yarub Hani Al Nuaimi <ahmedyarubhani@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2024-07-18T11:07:54Z
Lists: pgsql-hackers
On Wed, 10 Jul 2024 at 22:58, Tomas Vondra <tomas.vondra@enterprisedb.com> wrote: > IIRC long time ago VACUUM FULL actually worked in a similar way, i.e. by > moving rows around. I'm not sure if it did the lock-free thing as > proposed here (probably not), but I guess at least some of the reasons > why it was replaced by CLUSTER would still apply to this new thing. Yeah, that changed in 9.0. The old version still obtained an AEL on the table. I think the primary issue with the old way was index bloat wasn't fixed. The release notes for 9.0 do claim the CLUSTER method "is substantially faster in most cases", however, I imagine there are plenty of cases where it wouldn't be. e.g, it's hard to imagine rewriting the entire 1TB table and indexes is cheaper than moving 1 row out of place row. David
Commits
-
Support rewritten-based full vacuum as VACUUM FULL. Traditional
- 946cf229e89f 9.0.0 cited