Re: Reduce pinning in btree indexes - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: Reduce pinning in btree indexes
Date
Msg-id 87zj7z6ckc.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: Reduce pinning in btree indexes  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: Reduce pinning in btree indexes  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-hackers
>>>>> "Kyotaro" == Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> writes:
>> You might want to try running the same test, but after patching>> ExecSupportsMarkRestore to return false for index
scans.This will>> cause the planner to insert a Materialize node to handle the>> mark/restore.
 
Kyotaro> Mmm? The patch bt-nopin-v1.patch seems not contain the changeKyotaro> for ExecSupportMarkRestore and the very
simplefunction remainKyotaro> looking to return true for T_Index(Only)Scan after the patchKyotaro> applied.
 

Right. I'm suggesting you change that, in order to determine what
performance cost, if any, would result from abandoning the idea of doing
mark/restore entirely.

-- 
Andrew (irc:RhodiumToad)



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Merge compact/non compact commits, make aborts dynamically sized
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Reduce pinning in btree indexes