pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Justin King <kingpin867@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Cc: kgrittn@gmail.com
Subject: Re: PG12 autovac issues
Date: Sat, 28 Mar 2020 17:47:19 +0900
Message-ID: <20200328084719.GA29155@paquier.xyz> (raw)
In-Reply-To: <CAE39h20JGOjuwnOzSPhK_0xdscc5awwtxxf_Qe7W-xMxeNuuTQ@mail.gmail.com>
References: <20200323200051.qzyqvnips7o3ai4g@alap3.anarazel.de>
	<20200324052606.GE1836@paquier.xyz>
	<20200324054039.ulrxbzo2ycy7pu5i@alap3.anarazel.de>
	<20200324061238.GG1836@paquier.xyz>
	<20200324194259.pidupqxtqnquk4wu@alap3.anarazel.de>
	<CAE39h23EoQpGeBN4XDg5MhZZFz_AMbnr7O+h-Q=LXvS1ZuoXyQ@mail.gmail.com>
	<20200326014108.GA2199@paquier.xyz>
	<CAE39h20kVBn+wHGBapOyoDUSAq=6vTyO4KuoX4sHQtZfdpVi+A@mail.gmail.com>
	<20200327050622.GB2133@paquier.xyz>
	<CAE39h20JGOjuwnOzSPhK_0xdscc5awwtxxf_Qe7W-xMxeNuuTQ@mail.gmail.com>

On Fri, Mar 27, 2020 at 05:10:03PM -0500, Justin King wrote:
> Sounds great.  I will email you directly with a link!

Thanks.  From the logs, the infinite loop on which autovacuum jobs are
stuck is clear.  We have a repetitive number of anti-wraparound and
non-aggressive jobs happening for 7 shared relations every 5 seconds
or so and autovacuum is not able to do something else:
pg_auth_members
pg_authid
pg_database
pg_replication_origin
pg_shseclabel
pg_subscription
pg_tablespace

However I have found a correlation between all the tests I have done
on my own laptop, all the tests Julien and I have done in our internal
company buildfarm, and your logs.  We have 10 shared catalogs in the
system and the problem does not happen with the three following ones,
unable to trigger an anti-wraparound non-aggressive job:
pg_db_role_setting
pg_shdepend
pg_shdescription

Not sure yet what that is, but it is hard to believe that it is just a
coincidence.

> This is encouraging. As I mentioned, we have a workaround in place for
> the moment, but don't hesitate if you need anything else from me.
> Thanks for jumping in on the thread, it was nice validation to know
> that I wasn't the only one seeing the issue!

Yes.  We have been able to confirm that 2aa6e33 is a direct cause of
your problem.
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (44+ messages)  latest in thread

Message-ID: <20200328084719.GA29155@paquier.xyz>
Permalink:  ../20200328084719.GA29155@paquier.xyz/
Also on:    postgresql.org/message-id/20200328084719.GA29155@paquier.xyz

 · 

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-admin@postgresql.org
  Cc: michael@paquier.xyz, kingpin867@gmail.com, andres@anarazel.de, rjuju123@gmail.com, pgsql-general@lists.postgresql.org, kgrittn@gmail.com
  Subject: Re: PG12 autovac issues
  In-Reply-To: <20200328084719.GA29155@paquier.xyz>

* 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