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

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: a lot of shared buffers hit when planning for a simple query with primary access path
Дата
Msg-id CAApHDvoR17=B42zHe_QtPgcQdpHic5+nz8V0VqvbRsNxo3V5Zw@mail.gmail.com
обсуждение исходный текст
Ответ на a lot of shared buffers hit when planning for a simple query with primary access path  (James Pang <jamespang886@gmail.com>)
Ответы Re: a lot of shared buffers hit when planning for a simple query with primary access path
Список pgsql-performance
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.

David



В списке pgsql-performance по дате отправления: