Postgres Pro
Downloads
Home   >   mailing lists

Re: a lot of shared buffers hit when planning for a simple query with primary access path - Mailing list pgsql-performance

From David Rowley
Subject Re: a lot of shared buffers hit when planning for a simple query with primary access path
Date
Msg-id CAApHDvqzPxWv_HrN7NyhisWLcKBrhQyBT1sE9sM7aE5kZWRRmg@mail.gmail.com
Whole thread Raw
In response to Re: a lot of shared buffers hit when planning for a simple query with primary access path  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: a lot of shared buffers hit when planning for a simple query with primary access path
List pgsql-performance
Tree view 
On Mon, 1 Jul 2024 at 22:20, Pavel Stehule <pavel.stehule@gmail.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

pgsql-performance by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: a lot of shared buffers hit when planning for a simple query with primary access path
Next
From: James Pang
Date:
Subject: Re: a lot of shared buffers hit when planning for a simple query with primary access path