From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | David Rowley <dgrowleyml(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:20:15 |
Message-ID: | CAFj8pRAkhf3_T3vpga0K9C_fPgZe9QsFsgqDW2HtwSrkFbTP+A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi
po 1. 7. 2024 v 12:10 odesílatel David Rowley <dgrowleyml(at)gmail(dot)com> napsal:
> 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.
>
The planners get min/max range from indexes. So some user's indexes can be
bloated too with similar effect
Regards
Pavel
> David
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2024-07-01 10:52:03 | Re: a lot of shared buffers hit when planning for a simple query with primary access path |
Previous Message | David Rowley | 2024-07-01 10:10:08 | Re: a lot of shared buffers hit when planning for a simple query with primary access path |