Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute - Mailing list pgsql-bugs

From hubert depesz lubaczewski
Subject Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
Date
Msg-id aJSqb0zUoKZ05w8V@depesz.com
Whole thread Raw
In response to BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
List 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 by date:

Previous
From: Xuneng Zhou
Date:
Subject: Re: BUG #19006: Assert(BufferIsPinned) in BufferGetBlockNumber() is triggered for forwarded buffer
Next
From: Dilip Kumar
Date:
Subject: Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database