Re: Deleting older versions in unique indexes to avoid page splits
Victor Yegorov <vyegorov@gmail.com>
From: Victor Yegorov <vyegorov@gmail.com>
To: Peter Geoghegan <pg@bowt.ie>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-12-31T13:50:07Z
Lists: pgsql-hackers
чт, 31 дек. 2020 г. в 03:55, Peter Geoghegan <pg@bowt.ie>: > Attached is v12, which fixed bitrot against the master branch. This > version has significant comment and documentation revisions. It is > functionally equivalent to v11, though. > > I intend to commit the patch in the next couple of weeks. While it > certainly would be nice to get a more thorough review, I don't feel > that it is strictly necessary. The patch provides very significant > benefits with certain workloads that have traditionally been > considered an Achilles' heel for Postgres. Even zheap doesn't provide > a solution to these problems. The only thing that I can think of that > might reasonably be considered in competition with this design is > WARM, which hasn't been under active development since 2017 (I assume > that it has been abandoned by those involved). > I am planning to look into this patch in the next few days. -- Victor Yegorov
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Enhance nbtree index tuple deletion.
- d168b666823b 14.0 landed
-
Pass down "logically unchanged index" hint.
- 9dc718bdf2b1 14.0 landed
-
Fix index deletion latestRemovedXid bug.
- 422881744997 14.0 cited
-
Deprecate nbtree's BTP_HAS_GARBAGE flag.
- cf2acaf4dcb5 14.0 landed