Re: BUG #18419: Auto Vacuum In PostgreSQL 10.21

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: raut(dot)akshay89(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18419: Auto Vacuum In PostgreSQL 10.21
Date: 2024-04-04 01:13:30
Message-ID: CAApHDvqFD1PRR-BEb-vmekKcG0V1tjT7M-xTFJdvwofoPcFwPw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 4 Apr 2024 at 11:08, PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 18419
> Logged by: Akshay Raut
> Email address: raut(dot)akshay89(at)gmail(dot)com
> PostgreSQL version: Unsupported/Unknown
> Operating system: Windows 10
> Description:
>
> We are using PostgreSQL 10.21 in which we are deleting a few records
> periodically but we observed that the auto vacuum is not getting executed on
> all the tables.

> Is this a known issue with PostgreSQL and is there any solution to resolve
> this?

If you were doing something like calling pg_stat_reset() then the
counters might be getting reset before they're high enough for
autovacuum to care.

Otherwise, perhaps autovacuum is running flat out due to badly tuned
autovacuum settings.

version 10 is out of support, so if there was some bug in that
version, we wouldn't fix it anyway. v12 is the oldest supported
version, currently. https://www.postgresql.org/support/versioning/

David

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Noah Misch 2024-04-04 05:28:28 Re: BUG #18386: Slow connection access after 'vacuum full pg_attribute'
Previous Message PG Bug reporting form 2024-04-03 12:32:12 BUG #18419: Auto Vacuum In PostgreSQL 10.21