On Thu, Jun 11, 2015 at 9:32 PM, Qingqing Zhou
<zhouqq.postgres@gmail.com> wrote:
> On Fri, Jun 5, 2015 at 10:59 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> So I really doubt that anyone would have any enthusiasm for saddling btree
>> with a similar mechanism. It's complicated (and has been the cause of
>> multiple bugs); it's hard to figure out when is the optimal time to flush
>> the pending insertions; and it slows down searches in favor of making
>> inserts cheap, which is generally not the way to bet --- if that's the
>> tradeoff you want, why not drop the index altogether?
>
> Hint bits update is also painful in above case, but it is out of the topic here.
Are your records spread out around many transactions or so you tend to
have large batches all with the same xid?
merlin
