Re: Indirect indexes - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: Indirect indexes
Date
Msg-id CABOikdOFrQ=1i1A8jWQkWpVSCg--t4nfuPYhdNG97itCt2g=+Q@mail.gmail.com
Whole thread Raw
In response to Re: Indirect indexes  (Claudio Freire <klaussfreire@gmail.com>)
Responses Re: Indirect indexes  (Claudio Freire <klaussfreire@gmail.com>)
List pgsql-hackers


On Thu, Oct 20, 2016 at 9:20 PM, Claudio Freire <klaussfreire@gmail.com> wrote:


With indirect indexes, since you don't need to insert a tid, you can
just "insert on conflict do nothing" on the index.

Would that work with non-unique indexes? Anyways, the point I was trying to make is that there are a similar technical challenges and we could solve it for WARM as well with your work for finding conflicting <key, tid> pairs and then not doing inserts. My thinking currently is that it will lead to other challenges, especially around vacuum, but I could be wrong.

What I tried to do with initial WARM patch is to show significant improvement even with just 50% WARM updates, yet keep the patch simple. But there are of course several things we can do to improve it further and support other index types.

Thanks,
Pavan

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

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Renaming of pg_xlog and pg_clog
Next
From: Stephen Frost
Date:
Subject: Re: Renaming of pg_xlog and pg_clog