On Fri, Oct 11, 2024 at 5:00 PM Greg Sabino Mullane <htamfids@gmail.com> wrote:
if we have any column with large string/text values and we want it to be indexed then there is no choice but to go for a hash index. Please correct me if I'm wrong.
There are other strategies / solutions, but we would need to learn more about your use case.
Cheers,
Greg
Hi Respected Team
How do we enforce the secondary column of composite index to index scan on concurrent activity in postgres?
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 querying select * from test where id = '4234';
Value of id changes and during concurrent activity and cpu utilization increased too much that i have observed which means query plan changed why
I could see index scan with explain for it on singal call or double calls
Is there any way to keep an index scan for it during concurrency rather than a separate index on the second column of the composite index ?
