Re: Use of inefficient index in the presence of dead tuples

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alexander Staubo <alex(at)purefiction(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Use of inefficient index in the presence of dead tuples
Date: 2024-05-29 08:10:56
Message-ID: CAApHDvrrXUZ+u--+hv02XH=L8U=mZLbkk605ueVOohaOYcoFVQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 29 May 2024 at 12:53, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It would be interesting to see a non-artificial example that took
> into account when the last auto-vacuum and auto-analyze really
> happened, so we could see if there's any less-fragile way of
> dealing with this situation.

I think we need to find a way to give some additional preference to
using indexes with more keys matching to quals.

David

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Francisco Olarte 2024-05-29 08:23:38 Re: Memory issues with PostgreSQL 15
Previous Message Laurenz Albe 2024-05-29 08:08:29 Re: Long running query causing XID limit breach