From: Tom Lane <tgl@sss.pgh.pa.us>
To: Max Vikharev <bm.kinder@gmail.com>
Cc: Jeff Janes <jeff.janes@gmail.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16691: Autovacuum stops processing certain databases until postgresql rebooted
Date: Sun, 01 Nov 2020 12:01:38 -0500
Message-ID: <387272.1604250098@sss.pgh.pa.us> (raw)
In-Reply-To: <CACRpr1NLVbQ9o+Kv=R-CzO9fgtZAjKVoMHdmfPDoMrkDJYsyrA@mail.gmail.com>
References: <16691-e029ffaaf2e1e10c@postgresql.org>
<CAMkU=1yic6ADT9mSHQGzdUtzsp6u9R8xwzFv6Yj=ijVMXXGRvA@mail.gmail.com>
<CACRpr1NLVbQ9o+Kv=R-CzO9fgtZAjKVoMHdmfPDoMrkDJYsyrA@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, bm.kinder@gmail.com, jeff.janes@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16691: Autovacuum stops processing certain databases until postgresql rebooted
In-Reply-To: <387272.1604250098@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox