public inbox for [email protected]
help / color / mirror / Atom feedFrom: Siraj G <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: vacuuming taking long time for pg_attribute
Date: Fri, 17 Jan 2025 11:45:22 +0530
Message-ID: <CAC5iy63HKROj55PSZ3Ls7WmXVWi-DvRaqqRpp_7A6g1QTPAb=Q@mail.gmail.com> (raw)
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
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: vacuuming taking long time for pg_attribute
In-Reply-To: <CAC5iy63HKROj55PSZ3Ls7WmXVWi-DvRaqqRpp_7A6g1QTPAb=Q@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox