Re: vacuuming taking long time for pg_attribute

One other thing I would like to add..
While the performance was problem, our application jobs also failed and we
were unable to start them as internally they query pg_attribute.

Regards
Siraj

On Fri, Jan 17, 2025 at 11:45 AM Siraj G <tosiraj(dot)g(at)gmail(dot)com> wrote:

> Hello Experts!
>
> The PgSQL version is 16 and it runs in Cloud SQL managed by GCP.
>
> Problem was that we were unable to conveniently get the object details in
> the schema browser (within the Cloud SQL Studio) as it was getting timeout
> again and again. Several application jobs start to fail. Eventually we
> found that pg_catalog.pg_attribute was having tons of dead tuples. While
> vacuum on this took several hours, the problem got resolved eventually.
> Command ran: vacuum pg_attribute;
>
> I would like to understand how this issue can be prevented. We do have
> autovacuum ON and I could see the last vacuum on this table was just about
> 30hrs back.
>
> Appreciate any suggestions.
>
> Regards
> Siraj
>