On Sat, Jul 15, 2017 at 8:58 PM, Peter Geoghegan <p...@bowt.ie> wrote: > To repeat myself, for emphasis: *Not all bloat is equal*.
+1. > I strongly agree. I simply don't understand how you can adopt UNDO for > MVCC, and yet expect to get a benefit commensurate with the effort > without also implementing "retail index tuple deletion" first. I agree that we need retail index tuple deletion. I liked Claudio's idea at http://postgr.es/m/cagtbqpz-ktrqiaa13xg1gne461yowra-s-yccqptyfrpkta...@mail.gmail.com -- that seems indispensible to making retail index tuple deletion reasonably efficient. Is anybody going to work on getting that committed? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
