Re: Performance on JSONB select
| От | Michael Lewis |
|---|---|
| Тема | Re: Performance on JSONB select |
| Дата | |
| Msg-id | CAHOFxGpFn8+r+_RjRMkbUH0TY0DPhyaV=+JraTi8caZWBy7cZA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Performance on JSONB select (PegoraroF10 <marcos@f10.com.br>) |
| Ответы |
Re: Performance on JSONB select
Re: Performance on JSONB select |
| Список | pgsql-general |
Much of indexing strategy depends on knowing the data like how many distinct values and what the distribution is like. Is JsonBField->>'status' always set? Are those three values mentioned in this query common or rare? Can you re-write this query to avoid using an OR in the where clause? Are you just wanting to add a GIN index for the jsonb paths? Or do you want indexed like below that are a bit stylized to this query?
CREATE INDEX idx_MyTable_status USING btree( JsonBField->>'status' );
CREATE INDEX idx_MyTable_descartada_date USING btree( To_Date(JsonBField->'descartada'->>'data','yyyy-mm-dd') );
CREATE INDEX idx_MyTable_contrato_date USING btree( To_Date(JsonBField->'contrato'->>'data','yyyy-mm-dd') );
В списке pgsql-general по дате отправления: