pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ondřej Světlík <osvetlik@flexibee.eu>
To: pgsql-admin@postgresql.org
Subject: Autovacuum of pg_database
Date: Thu, 5 May 2016 17:16:01 +0200
Message-ID: <572B63B1.3030603@flexibee.eu> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Hello again,

we have another strange problem with autovacuum. The process goes well 
until it reaches the table pg_database (in some databases, not all), 
then it loops over it forever  (until I run vacuum full analyze on that 
table, simple vacuum doesn't help):

2016-05-05 17:13:33 CEST  34818LOG:  automatic vacuum of table 
"somedatabase.pg_catalog.pg_database": index scans: 0
	pages: 0 removed, 233 remain
	tuples: 0 removed, 5817 remain, 0 are dead but not yet removable
	buffer usage: 87 hits, 0 misses, 0 dirtied
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	system usage: CPU 0.00s/0.00u sec elapsed 0.00 sec
2016-05-05 17:13:33 CEST  34819LOG:  automatic vacuum of table 
"somedatabase.pg_catalog.pg_database": index scans: 0
	pages: 0 removed, 233 remain
	tuples: 0 removed, 5817 remain, 0 are dead but not yet removable
	buffer usage: 87 hits, 0 misses, 0 dirtied
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	system usage: CPU 0.00s/0.00u sec elapsed 0.00 sec
2016-05-05 17:13:33 CEST  34820LOG:  automatic vacuum of table 
"somedatabase.pg_catalog.pg_database": index scans: 0
	pages: 0 removed, 233 remain
	tuples: 0 removed, 5817 remain, 0 are dead but not yet removable
	buffer usage: 87 hits, 0 misses, 0 dirtied
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	system usage: CPU 0.00s/0.00u sec elapsed 0.00 sec
2016-05-05 17:13:34 CEST  34821LOG:  automatic vacuum of table 
"somedatabase.pg_catalog.pg_database": index scans: 0
	pages: 0 removed, 233 remain
	tuples: 0 removed, 5817 remain, 0 are dead but not yet removable
	buffer usage: 87 hits, 0 misses, 0 dirtied
	avg read rate: 0.000 MB/s, avg write rate: 0.000 MB/s
	system usage: CPU 0.00s/0.00u sec elapsed 0.00 sec

Not sure if it's a bug or I'm doing something wrong.

Thanks in advance,

Ondřej


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (28+ messages)  latest in thread

Message-ID: <572B63B1.3030603@flexibee.eu>
Permalink:  ../572B63B1.3030603@flexibee.eu/
Also on:    postgresql.org/message-id/572B63B1.3030603@flexibee.eu

 · 

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: osvetlik@flexibee.eu
  Subject: Re: Autovacuum of pg_database
  In-Reply-To: <572B63B1.3030603@flexibee.eu>

* 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