Re: BUG #16691: Autovacuum stops processing certain databases until postgresql rebooted - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16691: Autovacuum stops processing certain databases until postgresql rebooted
Date
Msg-id 387272.1604250098@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #16691: Autovacuum stops processing certain databases until postgresql rebooted  (Max Vikharev <bm.kinder@gmail.com>)
Responses Re: BUG #16691: Autovacuum stops processing certain databases until postgresql rebooted
List pgsql-bugs
Max Vikharev <bm.kinder@gmail.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



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16694: Server hangs in 100% CPU loop when decompressing a specific TOAST Postgis linestring
Next
From: Tom Lane
Date:
Subject: Re: BUG #16694: Server hangs in 100% CPU loop when decompressing a specific TOAST Postgis linestring