Re: Improving replay of XLOG_BTREE_VACUUM records

From: David Steele <david(at)pgmasters(dot)net>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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-03-10 00:29:10
Message-ID: 56E0BFD6.3020907@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/8/16 9:34 AM, Alvaro Herrera wrote:
> 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?

ISTM that this patch should be "returned with feedback" or "rejected"
based on the thread. I'm marking it "waiting for author" for the time
being.

Thanks,

--
-David
david(at)pgmasters(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2016-03-10 00:37:53 Re: [PROPOSAL] Client Log Output Filtering
Previous Message Petr Jelinek 2016-03-10 00:26:23 Re: Reworks of CustomScan serialization/deserialization