| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | Игорь Выскорко <vyskorko(dot)igor(at)yandex(dot)ru> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Jsonb first level keys statistic |
| Date: | 2020-01-28 17:42:10 |
| Message-ID: | CAHOFxGp593cbHyopE8_Bv_T1vL8mNXgOR=WhWgBy_nxHa-B82A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Other than creating a functional index on the keys that you most want to
access and include that function call in your query, I don't know that you
can. Functional indexes get statistics while partial indexes do not. If a
GIN index using path operator collected stats on the frequency of the keys,
then you would be all set I think. Perhaps that is a feature that could be
implemented.
Others will chime in I expect, but I tend to avoid using jsonb for any
values that I need to use to significant filter a result set (ON and WHERE
clauses).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicola Contu | 2020-01-29 08:34:27 | Re: ERROR: too many dynamic shared memory segments |
| Previous Message | Игорь Выскорко | 2020-01-28 13:50:07 | Jsonb first level keys statistic |