| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Indirect indexes |
| Date: | 2016-10-19 22:06:03 |
| Message-ID: | CAGTBQpZmC2SdvDQk5axJ7+0-0gckPr9VTjqs2DmK5cgbJNyatw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 19, 2016 at 2:04 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> What we should ask is what is the difference between indirect indexes
>> and WARM and to what extent they overlap.
>>
>> My current understanding is that WARM won't help you if you update
>> parts of a JSON document and/or use GIN indexes, but is effective
>> without needing to add a new index type and will be faster for
>> retrieval than indirect indexes.
>>
>> So everybody please chirp in with benefits or comparisons.
>
> I am not sure we have even explored all the limits of WARM with btree
> indexes --- I haven't heard anyone talk about non-btree indexes yet.
AFAIK there's no fundamental reason why it wouldn't work for other
index ams, but it does require quite a bit of legwork to get
everything working there.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-10-19 22:08:24 | Re: Patch: Implement failover on libpq connect level. |
| Previous Message | Merlin Moncure | 2016-10-19 19:39:02 | Re: emergency outage requiring database restart |