From: Matthew T. O'Connor <matthew@zeut.net>
To: Jeff Boes <jboes@nexcerpt.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: pg_autovacuum misinterpreting reltuples?
Date: Wed, 05 May 2004 14:25:36 -0400
Message-ID: <409931A0.4060608@zeut.net> (raw)
In-Reply-To: <40925870.50001@nexcerpt.com>
References: <40925870.50001@nexcerpt.com>
Jeff Boes wrote:
> We noticed that one of our high-volume insert tables was being vacuumed
> every time pg_autovacuum woke up. (I"m running it with the default
> threshold values, and a 900-second sleep cycle.) The table has a few
> million rows in it. With "debug = 2" on, here's what the pg_autovacuum
> log reports for this table:
>
> [2004-04-30 09:32:11 AM] table name: nexcerpt."public"."links"
> [2004-04-30 09:32:11 AM] relid: 1014188; relisshared: 0
> [2004-04-30 09:32:11 AM] reltuples: 3; relpages: 118888
>
> Note that "reltuples" is being reported as "3", which seems a bit low. Aha!
>
> # select reltuples from pg_class where relname = 'links';
> reltuples
> -------------
> 3.32127e+06
> (1 row)
>
> Is it possible that pg_autovacuum sees this value as "3"? Or is it just
> mis-formatting the value in the log?
Yes. This is a known bug inside of pg_autovacuum, it is fixed inside of
CVS, and will be released with 7.4.3 (whenever that happens, hopefully
soon since I'm getting lots of reports for this bug). Please downlooad
pg_autovacuum from CVS and compile by hand for the time being.
Matthew O'Connor
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-hackers@postgresql.org
Cc: matthew@zeut.net, jboes@nexcerpt.com
Subject: Re: pg_autovacuum misinterpreting reltuples?
In-Reply-To: <409931A0.4060608@zeut.net>
* 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