From: Tom Lane <tgl@sss.pgh.pa.us>
To: depesz@depesz.com
Cc: 1986comatose@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
Date: Thu, 07 Aug 2025 17:33:34 -0400
Message-ID: <1622268.1754602414@sss.pgh.pa.us> (raw)
In-Reply-To: <aJSqb0zUoKZ05w8V@depesz.com>
References: <19014-3b29e6cbcb5f0b82@postgresql.org>
<aJSqb0zUoKZ05w8V@depesz.com>
hubert depesz lubaczewski <depesz@depesz.com> writes:
> On Thu, Aug 07, 2025 at 07:47:58AM +0000, PG Bug reporting form wrote:
>> 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.
> I bet you have some long transaction somewhere, and this table is shared
> (same table visible in all databases).
Another theory, again remembering this is a shared catalog, is that
there is enough update traffic on pg_shdepend to justify constant
vacuuming. That could be plausible if there's a lot of object
creation and deletion going on (even just temporary tables, I think).
Anyway, I don't see any such behavior here after setting
log_autovacuum_min_duration = 0. We're going to need more
information to reproduce the problem.
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, depesz@depesz.com, 1986comatose@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
In-Reply-To: <1622268.1754602414@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox