pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: Mariel Cherkassky <mariel.cherkassky@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: autovacuum doesnt run on the pg_toast_id table
Date: Thu, 17 Jan 2019 11:46:51 -0600
Message-ID: <20190117174651.GC18438@telsasoft.com> (raw)
In-Reply-To: <CA+t6e1nd6odb2pzSASzzsUx6pTmTQ7EExjFuyRkmVh8cdm8QFw@mail.gmail.com>
References: <CA+t6e1nd6odb2pzSASzzsUx6pTmTQ7EExjFuyRkmVh8cdm8QFw@mail.gmail.com>

On Thu, Jan 17, 2019 at 07:28:52PM +0200, Mariel Cherkassky wrote:
...
> Now, I realized from the autovacuum
> logging, that when autovacuum runs on the original table (A) it doesn't
> necessary run on the toasted table and this is very weird.
...
> Any idea why the autovacuum doesnt vacuum both tables ?

It *does* vacuum both, just not *necessarily*, as you saw.

The toast is a separate table, so it's tracked separately.

Note that:
|If a table parameter value is set and the
|equivalent <literal>toast.</literal> parameter is not, the TOAST table
|will use the table's parameter value.

You could look in pg_stat_all_tables, to see how frequently the toast is being
autovacuumed relative to its table.

Justin




view thread (8+ messages)  latest in thread

Message-ID: <20190117174651.GC18438@telsasoft.com>
Permalink:  ../20190117174651.GC18438@telsasoft.com/
Also on:    postgresql.org/message-id/20190117174651.GC18438@telsasoft.com

 · 

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-performance@postgresql.org
  Cc: pryzby@telsasoft.com, mariel.cherkassky@gmail.com, pgsql-performance@lists.postgresql.org
  Subject: Re: autovacuum doesnt run on the pg_toast_id table
  In-Reply-To: <20190117174651.GC18438@telsasoft.com>

* 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