On Tue, 15 Oct, 2024, 15:15 David Rowley, wrote:
> On Sat, 12 Oct 2024 at 02:28, Durgamahesh Manne
> wrote:
> > Second column of composite index not in use effectively with index scan
> when using second column at where clause
> >
> > I have composite index on (placedon,id) of test
> > When quer
On Sat, 12 Oct 2024 at 02:28, Durgamahesh Manne
wrote:
> Second column of composite index not in use effectively with index scan when
> using second column at where clause
>
> I have composite index on (placedon,id) of test
> When quering select * from test where id = '4234';
> Value of id chan
On Fri, 11 Oct, 2024, 23:33 Durgamahesh Manne,
wrote:
>
>
> On Fri, Oct 11, 2024 at 9:57 PM Greg Sabino Mullane
> wrote:
>
>> On Fri, Oct 11, 2024 at 9:28 AM Durgamahesh Manne <
>> maheshpostgr...@gmail.com> wrote:
>>
>>> composite key (placedon,id)
>>> In concurrent mode if i use id at where cl
On Fri, Oct 11, 2024 at 9:57 PM Greg Sabino Mullane
wrote:
> On Fri, Oct 11, 2024 at 9:28 AM Durgamahesh Manne <
> maheshpostgr...@gmail.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 mitiga
On Fri, Oct 11, 2024 at 9:28 AM Durgamahesh Manne
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)
-- Forwarded message -
From: Durgamahesh Manne
Date: Mon, Oct 7, 2024 at 10:01 AM
Subject: Inefficient use of index scan on 2nd column of composite index
during concurrent activity
To:
Hi team
Second column of composite index not in use effectively with index scan
when using
