Re: Establishing a local connection to PostgreSQL 9.6 takes seconds
От | Marcin Barczynski |
---|---|
Тема | Re: Establishing a local connection to PostgreSQL 9.6 takes seconds |
Дата | |
Msg-id | CAOhG4weUaCADCMBw_26kNPp5n0_dMsjA02UxGBbnPoaHxocUEA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Establishing a local connection to PostgreSQL 9.6 takes seconds (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Establishing a local connection to PostgreSQL 9.6 takes seconds
|
Список | pgsql-general |
Thanks for the immediate reply.
It turned out to be pg_attribute. It was bloated probably due to the large number of temp tables created.
Are there any recommendations on how to prevent such a bloat from happening?
It turned out to be pg_attribute. It was bloated probably due to the large number of temp tables created.
Are there any recommendations on how to prevent such a bloat from happening?
On Wed, Jun 16, 2021 at 4:10 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Marcin Barczynski <mbarczynski@starfishstorage.com> writes:
> It's always /opt/prod/pg/9.6/base/18370/1108887031. Unfortunately, no trace
> of it in pg_class:
It's probably a mapped system catalog, which will have relfilenode = 0.
Try
SELECT relname FROM pg_class WHERE pg_relation_filenode(oid) = 1108887031;
My guess is that whichever catalog it is is badly bloated.
regards, tom lane
Marcin Barczyński | Senior Software Engineer |![]()
mbarczynski@starfishstorage.com | http://www.starfishstorage.com
В списке pgsql-general по дате отправления: