Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
| От | hubert depesz lubaczewski |
|---|---|
| Тема | Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute |
| Дата | |
| Msg-id | aJSqb0zUoKZ05w8V@depesz.com обсуждение |
| Ответ на | BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute (PG Bug reporting form <noreply@postgresql.org>) |
| Ответы |
Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
|
| Список | pgsql-bugs |
On Thu, Aug 07, 2025 at 07:47:58AM +0000, PG Bug reporting form wrote: > The following bug has been logged on the website: > We only actively use the ecount database, yet our logs show that an > automatic “aggressive” VACUUM is repeatedly running on > template0.pg_catalog.pg_shdepend and template1.pg_catalog.pg_shdepend at > roughly one-minute intervals. Since the template databases aren’t used for > normal operations, these vacuums seem unnecessary and are consuming system > resources. We believe this behavior is a bug. Please check what is: select now() - xact_start from pg_stat_activity order by xact_start asc nulls last limit 1 I bet you have some long transaction somewhere, and this table is shared (same table visible in all databases). Best regards, depesz
В списке pgsql-bugs по дате отправления: