Re: Inefficient use of index scan on 2nd column of composite index during concurrent activity

[Greg Sabino Mullane <htamfids@xxxxxxxxx>]

On Fri, Oct 11, 2024 at 9:28 AM Durgamahesh Manne <maheshpostgres9@xxxxxxxxx> 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