pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: hubert depesz lubaczewski <depesz@depesz.com>
To: 1986comatose@gmail.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
Date: Thu, 7 Aug 2025 15:30:23 +0200
Message-ID: <aJSqb0zUoKZ05w8V@depesz.com> (raw)
In-Reply-To: <19014-3b29e6cbcb5f0b82@postgresql.org>
References: <19014-3b29e6cbcb5f0b82@postgresql.org>

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







view thread (4+ messages)  latest in thread

Message-ID: <aJSqb0zUoKZ05w8V@depesz.com>
Permalink:  ../aJSqb0zUoKZ05w8V@depesz.com/
Also on:    postgresql.org/message-id/aJSqb0zUoKZ05w8V@depesz.com

 · 

reply

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: 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: <aJSqb0zUoKZ05w8V@depesz.com>

* 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