BUG #18419: Auto Vacuum In PostgreSQL 10.21

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: raut(dot)akshay89(at)gmail(dot)com
Subject: BUG #18419: Auto Vacuum In PostgreSQL 10.21
Date: 2024-04-03 12:32:12
Message-ID: 18419-b07f7f19ff1227a2@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

Due to this, we are not able to get the space held by the dead rows back to
the database and at some point in time our system runs out of space.

All the tables have adequate data and the deleted rows are also beyond the
scale factor and auto vacuum threshold.

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

This issue has become very critical for us and any help will be highly
appreciated.

Thanks.

Regards,
Akshay Raut

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2024-04-04 01:13:30 Re: BUG #18419: Auto Vacuum In PostgreSQL 10.21
Previous Message Michael Zhilin 2024-04-03 05:08:26 Re: BUG: deadlock between autovacuum worker and client backend during removal of orphan temp tables with sequences