pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Joseph Hammerman <joe.hammerman@datadoghq.com>
To: pgsql-admin@postgresql.org
Subject: Re: Monitoring autovacuum induced contention
Date: Thu, 07 Dec 2023 04:16:40 +0100
Message-ID: <1797104bd3deefa7385f70aea665ac5c0a54e8ea.camel@cybertec.at> (raw)
In-Reply-To: <CAHs7QM95WgOWBdhtjpbg489A77yLqM6MFOi7qw2BPVNqn3qmeg@mail.gmail.com>
References: <CAHs7QM95WgOWBdhtjpbg489A77yLqM6MFOi7qw2BPVNqn3qmeg@mail.gmail.com>

On Wed, 2023-12-06 at 13:35 -0800, Joseph Hammerman wrote:
> We are working on tuning autovacuum correctly. While the biggest problem we have
> and most other OLTP deployments I have seen have is autovacuum resource starvation,
> I'd like to be able to reliably determine when we have turned autovacuum capacity
> dials too far.
> 
> Is there any way to track autovacuum induced query waits?

Autovacuum won't directly block you, so you will never see a process waiting for
autovacuum.  The exception to this rule is that statements that take high locks,
like CREATE INDEX or TRUNCATE, may be seen waiting for autovacuum to complete
occasionally.  But that is probably not your problem.

Autovacuum will compete for system resources with your normal workload.
So you should monitor operating system resources like CPU or disk I/O, and if
any of these is at capacity while autovacuum is processing a table, you will
feel the impact.

Yours,
Laurenz Albe





view thread (2+ messages)

Message-ID: <1797104bd3deefa7385f70aea665ac5c0a54e8ea.camel@cybertec.at>
Permalink:  ../1797104bd3deefa7385f70aea665ac5c0a54e8ea.camel@cybertec.at/
Also on:    postgresql.org/message-id/1797104bd3deefa7385f70aea665ac5c0a54e8ea.camel@cybertec.at

 · 

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: laurenz.albe@cybertec.at, joe.hammerman@datadoghq.com
  Subject: Re: Monitoring autovacuum induced contention
  In-Reply-To: <1797104bd3deefa7385f70aea665ac5c0a54e8ea.camel@cybertec.at>

* 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