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 Pavel Stehule
Subject Re: a lot of shared buffers hit when planning for a simple query with primary access path
Date
Msg-id CAFj8pRAkhf3_T3vpga0K9C_fPgZe9QsFsgqDW2HtwSrkFbTP+A@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  (David Rowley <dgrowleyml@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
Hi

po 1. 7. 2024 v 12:10 odesílatel David Rowley <dgrowleyml@gmail.com> napsal:
On Mon, 1 Jul 2024 at 21:45, James Pang <jamespang886@gmail.com> wrote:
>    Buffers: shared hit=110246         <<< here planning need access a lot of buffers
>  Planning Time: 81.850 ms
>  Execution Time: 0.034 ms
>
>    could you help why planning need a lot of shared buffers access ?

Perhaps you have lots of bloat in your system catalogue tables. That
could happen if you make heavy use of temporary tables. There are many
other reasons too. It's maybe worth doing some vacuum work on the
catalogue tables.

The planners get min/max range from indexes. So some user's indexes can be bloated too with similar effect

Regards

Pavel


David


pgsql-performance by date:

Previous
From: David Rowley
Date:
Subject: Re: a lot of shared buffers hit when planning for a simple query with primary access path
Next
From: David Rowley
Date:
Subject: Re: a lot of shared buffers hit when planning for a simple query with primary access path