pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Max Vikharev <bm.kinder@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16620: Autovacuum does not process certain databases after migration from postgresql 10
Date: Wed, 16 Sep 2020 21:19:54 -0400
Message-ID: <98503.1600305594@sss.pgh.pa.us> (raw)
In-Reply-To: <CACRpr1NiocLO892S=8zXbRZrXkbL6dLNia+Jpt6RpiVYqNw3hA@mail.gmail.com>
References: <16620-57ee4c2e1b7b5fef@postgresql.org>
	<CACRpr1NiocLO892S=8zXbRZrXkbL6dLNia+Jpt6RpiVYqNw3hA@mail.gmail.com>

Max Vikharev <bm.kinder@gmail.com> writes:
> Problem gone after restarting the cluster.
> Autovacuum started to process relations in other databases.

Hmm, interesting.

> I dont know how to reproduce the issue, we will monitor it.
> If there any way to debug it when it occurs again - let me know.

Did you by any chance capture the contents of pg_database.datfrozenxid
and datminmxid and compare them to the pg_class.relfrozenxid and
relminmxid fields in the problematic databases?

It's not hard to imagine that if the pg_database fields somehow
didn't get updated correctly during pg_upgrade, that would prevent
autovacuum from processing some databases to prevent wraparound.
However, that doesn't explain failure to examine those databases
at all, so I'm a bit at a loss.

Another thing to check is whether the stats collector is working.
Specifically look at whether counts in pg_stat_all_tables are
incrementing in the problem databases.

My guess is that somehow pg_upgrade left something in a slightly
hosed state, and that restarting de-hosed it, so that you aren't
going to see this again ... at least not till your next upgrade.
But I don't know exactly what the something could be.

			regards, tom lane





view thread (5+ messages)  latest in thread

Message-ID: <98503.1600305594@sss.pgh.pa.us>
Permalink:  ../98503.1600305594@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/98503.1600305594@sss.pgh.pa.us

 · 

reply

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, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16620: Autovacuum does not process certain databases after migration from postgresql 10
  In-Reply-To: <98503.1600305594@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