From: | Marcin Barczynski <mbarczynski(at)starfishstorage(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Establishing a local connection to PostgreSQL 9.6 takes seconds |
Date: | 2021-06-16 14:47:33 |
Message-ID: | CAOhG4weUaCADCMBw_26kNPp5n0_dMsjA02UxGBbnPoaHxocUEA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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?
On Wed, Jun 16, 2021 at 4:10 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Marcin Barczynski <mbarczynski(at)starfishstorage(dot)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(at)starfishstorage(dot)com | http://www.starfishstorage.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-06-16 14:55:13 | Re: Establishing a local connection to PostgreSQL 9.6 takes seconds |
Previous Message | Tom Lane | 2021-06-16 14:10:11 | Re: Establishing a local connection to PostgreSQL 9.6 takes seconds |