pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: alessandro.ferraresi1@gmail.com
Subject: BUG #16098: unexplained autovacuum to prevent wraparound
Date: Thu, 07 Nov 2019 15:06:22 +0000
Message-ID: <16098-3cb504cdc1b321a1@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16098
Logged by:          Alessandro Ferraresi
Email address:      alessandro.ferraresi1@gmail.com
PostgreSQL version: 10.6
Operating system:   RHEL 7
Description:        

Hello there,

I'm experiencing a weird behavior on 10.6 where I see autovacuum running to
prevent wraparound even if autovacuum_freeze_max_age is far away.
The database is brand-new and some tables have been loaded (using copy
command), below some details/parameters:  

pgxxxx=> show autovacuum_freeze_max_age;
 autovacuum_freeze_max_age
---------------------------
 200000000

 oldest_current_xid | percent_towards_wraparound |
percent_towards_emergency_autovac
--------------------+----------------------------+-----------------------------------
               3210 |                          0 |                          
      0

The tables involved have these custom parameters:

Options: 
fillfactor=80, 
autovacuum_enabled=true, 
autovacuum_vacuum_scale_factor=0.00, 
autovacuum_analyze_scale_factor=0.00, 
autovacuum_vacuum_threshold=500000, 
autovacuum_analyze_threshold=50000

From pg stat activity:

       age               | state  |   backend_type                          
                        query
-----------------------+--------+---------------------------+---------------------------------------------------------------------------------
00:18:32.899444 | active | autovacuum worker | autovacuum: VACUUM
haas.table1 (to prevent wraparound)
00:26:57.660416 | active | autovacuum worker | autovacuum: VACUUM
haas.table2 (to prevent wraparound)
00:26:54.848344 | active | autovacuum worker | autovacuum: VACUUM
haas.table3 (to prevent wraparound)

What could be the root cause of this? I believe this is  a bug as I can't
find any other explanation.

Thanks
Alessandro



view thread (8+ messages)  latest in thread

Message-ID: <16098-3cb504cdc1b321a1@postgresql.org>
Permalink:  ../16098-3cb504cdc1b321a1@postgresql.org/
Also on:    postgresql.org/message-id/16098-3cb504cdc1b321a1@postgresql.org

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, alessandro.ferraresi1@gmail.com
  Subject: Re: BUG #16098: unexplained autovacuum to prevent wraparound
  In-Reply-To: <16098-3cb504cdc1b321a1@postgresql.org>
  References: <16098-3cb504cdc1b321a1@postgresql.org>

* 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