BUG #16691: Autovacuum stops processing certain databases until postgresql rebooted

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: bm(dot)kinder(at)gmail(dot)com
Subject: BUG #16691: Autovacuum stops processing certain databases until postgresql rebooted
Date: 2020-10-29 21:24:50
Message-ID: 16691-e029ffaaf2e1e10c@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: 16691
Logged by: Max Vikharev
Email address: bm(dot)kinder(at)gmail(dot)com
PostgreSQL version: 12.3
Operating system: Ubuntu 16.04.5 LTS
Description:

Hi,

Previously i've reported BUG # 16620. But there is no answer on my new
mails, so i have to open this new report.

Currently we have to restart postgresql 12.3 every 5-7 days to make it work
properly on 5 terabyte cluster with ~ 50 databases. The problem is that
autovacuum stops to process certain databases and cycles on the only one...
Until we restart cluster.

We've made a trigger and now detecting very situation when it happen. And it
happen every 5-7 day.
So postgresql is loosing actual statistic, we see not effecttive plans, we
need to restart postgresql and also we have to run vacuum full explicitly
frequently. So this all is huge headake.

Please help us investigate the roots of problem.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2020-10-30 04:13:06 Re: BUG #16577: Segfault on altering a table located in a dropped tablespace
Previous Message Tom Lane 2020-10-29 21:02:00 Re: BUG #16690: database connection aborted with a signal 9 when query is run on MacOS Catalina