On Fri, Mar 2, 2018 at 7:06 PM, Aleksander Alekseev <a.aleks...@postgrespro.ru> wrote: > Hello Amit, > >> Sometime back Robert has proposed a solution to reduce the bloat in >> PostgreSQL [1] which has some other advantages of its own as well. To >> recap, in the existing heap, we always create a new version of a tuple on >> an update which must eventually be removed by periodic vacuuming or by >> HOT-pruning, but still in many cases space is never reclaimed completely. >> A similar problem occurs for tuples that are deleted. This leads to bloat >> in the database. > > This is an impressive work! >
Thanks. > Personally I would like to note that performance is probably not a > priority at this stage. > Right, but we are also trying to see that we just don't fall off the cliff for some more common workloads. > Most important parts, in my humble opinion at > least, are correctness, maintainability (tests, documentation, how > readable the code is), extendability (e.g. an ability to add point in > time recovery in the future), interfaces and heap format. > +1. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com