From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | depesz(at)depesz(dot)com |
Cc: | 1986comatose(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute |
Date: | 2025-08-07 21:33:34 |
Message-ID: | 1622268.1754602414@sss.pgh.pa.us |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
hubert depesz lubaczewski <depesz(at)depesz(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2025-08-07 23:39:24 | Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c |
Previous Message | Peter Praxmarer | 2025-08-07 20:15:06 | Re: BUG: IS NOT NULL on RECORD variable fails in 17.5-dev |