| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Inefficient use of index scan on 2nd column of composite index during concurrent activity |
| Date: | 2024-10-11 16:26:40 |
| Message-ID: | CAKAnmmJsqAPNbN8GKzJURwqTNAi+vTQVe2TbvE+BY0t=4K8ARQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-in-general |
On Fri, Oct 11, 2024 at 9:28 AM Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com>
wrote:
> composite key (placedon,id)
> In concurrent mode if i use id at where clause then query plan for that id
> column changes
>
> How to mitigate it rather than use seperate index for id to continue
> without change in query plan (index scan) during concurrent activity
>
Why the focus on "concurrent mode"? Perhaps explain what you mean by that.
Speaking of explain, it might help if you show us the explain plans and how
they are not coming out how you want. Also the table definitions, but feel
free to not show columns unrelated to the problem.
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-10-11 16:32:32 | Re: Connection between PostgreSQL and SAP HANA database |
| Previous Message | Adrian Klaver | 2024-10-11 16:16:30 | Re: Connection between PostgreSQL and SAP HANA database |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Durgamahesh Manne | 2024-10-11 18:03:15 | Re: Inefficient use of index scan on 2nd column of composite index during concurrent activity |
| Previous Message | Durgamahesh Manne | 2024-10-11 13:31:50 | Fwd: Inefficient use of index scan on 2nd column of composite index during concurrent activity |