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: James Pang <jamespang886(at)gmail(dot)com>
Cc: 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:10:08
Message-ID: CAApHDvoR17=B42zHe_QtPgcQdpHic5+nz8V0VqvbRsNxo3V5Zw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, 1 Jul 2024 at 21:45, James Pang <jamespang886(at)gmail(dot)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.

David

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next 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
Previous Message James Pang 2024-07-01 09:45:29 a lot of shared buffers hit when planning for a simple query with primary access path