Re: [HACKERS] Pluggable storage - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Pluggable storage
Date
Msg-id CA+TgmoZwsjtEprvXrTU5FmiN=Gi8i_x_gYjWzi5woOscUDqgiw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Pluggable storage  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: [HACKERS] Pluggable storage
List pgsql-hackers
On Sat, Jul 15, 2017 at 8:58 PM, Peter Geoghegan <pg@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-ycCQPtyFrpKTaDBQ@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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Pluggable storage
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Using non-sequential timelines in order to help with possible collisions