Date: Thu, 7 Aug 2025 15:30:23 +0200
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: 1986comatose@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19014: Automatic aggressive VACUUM on template0 and
 template1 pg_shdepend runs every minute
Message-ID: <aJSqb0zUoKZ05w8V@depesz.com>
Reply-To: depesz@depesz.com
References: <19014-3b29e6cbcb5f0b82@postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <19014-3b29e6cbcb5f0b82@postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/aJSqb0zUoKZ05w8V%40depesz.com>
Precedence: bulk

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