From: | Thomas Boussekey <thomas(dot)boussekey(at)gmail(dot)com> |
---|---|
To: | Inzamam Shafiq <inzamam(dot)shafiq(at)hotmail(dot)com> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Autovacuum on sys tables |
Date: | 2022-12-18 11:01:52 |
Message-ID: | CALUeYmcZixsxCq7aU=Pb+AVkUGgR5y+WYf5h=EcivtinoWQymg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello Inzamam,
Le sam. 17 déc. 2022 à 08:16, Inzamam Shafiq <inzamam(dot)shafiq(at)hotmail(dot)com> a
écrit :
> Dear Experts,
>
> Hope you are doing well.
>
> I have a question that autovacuum is running on sys tables like pg_class,
> pg_attribute, is it a normal thing? Further, what is dead tuples are not
> removed from Autovacuum, can we remove the dead tuples using FULL VACUUMM
> or pg_repack on sys tables?
>
pg_repack cannot run on system tables, it will FAIL with an explicit error
message explaining the limitation.
Each time you perform DDL operations (CREATE, DROP, ALTER), rows are
inserted/updated or deleted into the system tables : pg_class, pg_attribute
...
Autovacuum operations perform "low-level" operations, it can be interesting
to perform "middle-level" vacuum with VACUUM ANALYZE... that is not
blocking, but will be more a resource-consuming operation than autovacuum.
Performing VACUUM FULL operation will block access to these pillar tables
of your database.
If your application/users can handle it, go ahead!
At work on this kind of operation, I set a statement_timeout, in order to
properly stop the process if it is over a defined amount of time.
Hope this helps,
Thomas
>
> Thank you.
>
> Regards,
>
> *Inzamam Shafiq*
> *Sr. DBA*
>
From | Date | Subject | |
---|---|---|---|
Next Message | Inzamam Shafiq | 2022-12-19 06:12:29 | Re: Autovacuum on sys tables |
Previous Message | Tom Lane | 2022-12-18 04:20:45 | Re: integer square root function proposed |