pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Andres Freund <andres@anarazel.de>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: Justin King <kingpin867@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Cc: kgrittn@gmail.com
Subject: Re: PG12 autovac issues
Date: Tue, 24 Mar 2020 15:12:38 +0900
Message-ID: <20200324061238.GG1836@paquier.xyz> (raw)
In-Reply-To: <20200324054039.ulrxbzo2ycy7pu5i@alap3.anarazel.de>
References: <CAE39h22XLA7A=05RezvcTmEp=A369vRScToP5iLdTwArKiAuoA@mail.gmail.com>
	<20200319235626.wz4b57hbhuuy4w7j@alap3.anarazel.de>
	<CAE39h23xR9F8qbo5vj9+KL1nFnnTaYJrFde0BtWczQy_+De39Q@mail.gmail.com>
	<20200320190317.gdxwzexdfutymqs6@alap3.anarazel.de>
	<20200323152247.GB52612@nol>
	<20200323162303.s7ay5hjdvimtkz6u@alap3.anarazel.de>
	<20200323194725.GC52612@nol>
	<20200323200051.qzyqvnips7o3ai4g@alap3.anarazel.de>
	<20200324052606.GE1836@paquier.xyz>
	<20200324054039.ulrxbzo2ycy7pu5i@alap3.anarazel.de>

On Mon, Mar 23, 2020 at 10:40:39PM -0700, Andres Freund wrote:
> On 2020-03-24 14:26:06 +0900, Michael Paquier wrote:
>> Nothing really fancy:
>> - autovacuum_vacuum_cost_delay to 2ms (default of v12, but we used it
>> in v11 as well).
>> - autovacuum_naptime = 15s
>> - autovacuum_max_workers = 6
>> - log_autovacuum_min_duration = 0
> 
> Oh, so you're also involved in this? I'm starting to get a bit confused
> as to who is reporting what.

Yeah, sort of.  Julien has done a lot of work on that and I have an
access to the data and test beds, so we are just saying the same
things.

> Well, there's no logging of autovacuum launchers that don't do anything
> due to the "skipping redundant" logic, with normal log level. If somehow
> the horizon logic of autovacuum workers gets out of whack with what
> vacuumlazy.c does, then you'd not get any vacuums. But a usage level
> triggered analyze could still happen on such a table, I think.

What surprised me the most is that the same table happened to be
analyzed again and again after the launcher began its blackout.

> While looking at this issue I found a few problems, btw. That seems more
> like a -hackers discussion, so I started:
> https://postgr.es/m/20200323235036.6pje6usrjjx22zv3%40alap3.anarazel.de

Yes, let's discuss there.

> I think I might just have figured out another one...

Ouch.
--
Michael

Attachments:

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

view thread (44+ messages)  latest in thread

Message-ID: <20200324061238.GG1836@paquier.xyz>
Permalink:  ../20200324061238.GG1836@paquier.xyz/
Also on:    postgresql.org/message-id/20200324061238.GG1836@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, andres@anarazel.de, rjuju123@gmail.com, kingpin867@gmail.com, pgsql-general@lists.postgresql.org, kgrittn@gmail.com
  Subject: Re: PG12 autovac issues
  In-Reply-To: <20200324061238.GG1836@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