Re: a lot of shared buffers hit when planning for a simple query with primary access path

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: James Pang <jamespang886(at)gmail(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: a lot of shared buffers hit when planning for a simple query with primary access path
Date: 2024-07-01 10:52:03
Message-ID: CAApHDvqzPxWv_HrN7NyhisWLcKBrhQyBT1sE9sM7aE5kZWRRmg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, 1 Jul 2024 at 22:20, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> The planners get min/max range from indexes. So some user's indexes can be bloated too with similar effect

I considered that, but it doesn't apply to this query as there are no
range quals.

David

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message James Pang 2024-07-01 10:58:37 Re: a lot of shared buffers hit when planning for a simple query with primary access path
Previous Message Pavel Stehule 2024-07-01 10:20:15 Re: a lot of shared buffers hit when planning for a simple query with primary access path