Re: Improving replay of XLOG_BTREE_VACUUM records

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Vladimir Borodin <root(at)simply(dot)name>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improving replay of XLOG_BTREE_VACUUM records
Date: 2016-01-08 14:34:23
Message-ID: 20160108143423.GA577425@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
> On 8 January 2016 at 13:36, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:

> > I would agree except for the observation on toast indexes. I think
> > that's an important enough use case that perhaps we should have both.
>
> The exclusion of toast indexes is something we can remove also, I have
> recently discovered. When we access toast data we ignore MVCC, but we still
> have the toast pointer and chunkid to use for rechecking our scan results.
> So a later patch will add some rechecks.

Ah, interesting, glad to hear. I take it you're pushing your patch
soon, then?

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2016-01-08 14:39:31 Re: New feature "... ALTER CONSTRAINT ... VERIFY USING INDEX"
Previous Message Simon Riggs 2016-01-08 14:32:39 Re: New feature "... ALTER CONSTRAINT ... VERIFY USING INDEX"