| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Дмитрий Иванов <firstdismay(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Index creation |
| Date: | 2022-06-19 19:08:20 |
| Message-ID: | CAKFQuwY0kww1BGk4-KhiLZRq=v1ygCUnav_QGo27QfAj1kFreA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Jun 19, 2022 at 12:06 PM Дмитрий Иванов <firstdismay(at)gmail(dot)com>
wrote:
> Good afternoon.
> I have a query parser question. If there are two kinds of queries using an
> indexed field. In this case, one view is limited to this field, the second
> one uses a number of fields included in the index by the include directive.
> It makes sense to have two indexes, lightweight and containing include. Or
> will the plan rely on the nearest suitable index without considering its
> weight?
>
>
The system should avoid the larger sized index unless it will sufficiently
benefit from the Index Only Scan that such a larger covering index is
supposed to facilitate.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryn Llewellyn | 2022-06-19 21:31:11 | Outer joins and NULLs (old subject "ERROR: failed to find conversion function from key_vals_nn to record[]") |
| Previous Message | Дмитрий Иванов | 2022-06-19 19:05:45 | Index creation |