From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Valery Komarov <komarov(at)valerka(dot)net> |
Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Build or update inarray GIST index very slow. |
Date: | 2018-03-09 22:36:22 |
Message-ID: | CAMkU=1xA4G9sQyo3iOim798u=_AFo_ct+8pU+JrAPGxazoAWQw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Mar 9, 2018 at 1:53 PM, Valery Komarov <komarov(at)valerka(dot)net> wrote:
> Build or update inarray GIST index very very slow.
>
>
Yes, it is. I think there is room for improvement for the algorithm for
picking the pivot.
But in documentation "As a rule of thumb, a GIN index is faster to search
> than a GiST index, but slower to build or update; so GIN is better suited
> for static data and GiST for often-updated data."
>
Rules of thumb are not always true, that is what makes them rules of thumb.
Also, note that that sentence was removed from the documentation in 9.5
onward (commit 8e1ad1b37c7afdf99). I can't find the mailing-list thread
discussing it, but I think that that advice was deemed too vague to be
useful.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-03-09 22:44:15 | Re: Unrecognized exception condition "deprecated_feature" |
Previous Message | Kouber Saparev | 2018-03-09 22:28:48 | Re: Unrecognized exception condition "deprecated_feature" |