| From: | Олег Самойлов <splarv(at)ya(dot)ru> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: WTF with hash index? |
| Date: | 2018-11-13 20:52:26 |
| Message-ID: | 7E931A8C-2CDE-43EC-8777-3EEFD43EF27B@ya.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ah, thanks. I am not a developer of PostgreSQL. I am a developer in PostgreSQL. :) And I see two hash indexes on the same data and one of them 43 times bigger then other, this looked like something terribly wrong. Just free idea how to considerably improve your product.
> 13 нояб. 2018 г., в 22:37, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> написал(а):
>
> On 2018-Nov-13, Олег Самойлов wrote:
>
>> Very much better. What about to copy paste algorithm from
>> gin(jsonb_path_ops) to the hash index?
>
> You're welcome to submit patches.
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeffrey Kamei | 2018-11-13 22:42:51 | <-> Operator on Trigram Index |
| Previous Message | Alvaro Herrera | 2018-11-13 19:37:23 | Re: WTF with hash index? |