Re: Minmax indexes - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Minmax indexes
Date
Msg-id CA+U5nMLKd65=3YoMUdz8yX7aN4sEA-X009ADc_q-uQoi_br-BQ@mail.gmail.com
Whole thread Raw
In response to Re: Minmax indexes  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Minmax indexes
List pgsql-hackers
On 8 August 2014 16:03, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:

> 1. MMTuple contains the block number of the heap page (range) that the tuple
> represents. Vacuum is no longer needed to clean up old tuples; when an index
> tuples is updated, the old tuple is deleted atomically with the insertion of
> a new tuple and updating the revmap, so no garbage is left behind.

What happens if the transaction that does this aborts? Surely that
means the new value is itself garbage? What cleans up that?

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Reporting the commit LSN at commit time
Next
From: Fabien COELHO
Date:
Subject: Re: parametric block size?