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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Max Vikharev <bm(dot)kinder(at)gmail(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16691: Autovacuum stops processing certain databases until postgresql rebooted
Date: 2020-11-01 17:01:38
Message-ID: 387272.1604250098@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Max Vikharev <bm(dot)kinder(at)gmail(dot)com> writes:
>> finishing that table and moving to another in the same database

> Yes, that case. Vacuum processes relations in one database In cycle

It sounds like it's failing to advance that database's datfrozenxid
and/or datminmxid. You might try to figure out which table is holding
those values back by comparing pg_class.relfrozenxid and relminmxid
to those pg_database columns. Then look to see if autovacuum is
failing on that table, and/or try a manual vacuum to see what happens.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2020-11-01 21:57:36 Re: BUG #16694: Server hangs in 100% CPU loop when decompressing a specific TOAST Postgis linestring
Previous Message PG Bug reporting form 2020-11-01 16:51:56 BUG #16694: Server hangs in 100% CPU loop when decompressing a specific TOAST Postgis linestring