Re: pg_class reltuples/relpages not updated by autovacuum/vacuum

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Florian Helmberger <fh(at)25th-floor(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_class reltuples/relpages not updated by autovacuum/vacuum
Date: 2011-05-25 02:47:49
Message-ID: 25017.1306291669@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

Florian Helmberger <fh(at)25th-floor(dot)com> writes:
> I'm running a production database with PostgreSQL 9.0.3 (64-bit) on
> Debian 5.0.4 and have an issue with a TOAST table and far to frequent
> autovacuum runs.

> I think I've pinned the problem down to the values pg_class holds for
> the affected TOAST table:

> relpages | 433596
> reltuples | 1868538

> These values are significantly too low. Interestingly, the autovacuum
> logout reports the correct values:

> pages: 0 removed, 34788136 remain
> tuples: 932487 removed, 69599038 remain

> but these aren't stored in pg_class after each run.

That's exceedingly weird. Do the pg_stat_all_tables columns update
after autovacuums on that table?

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Florian Helmberger 2011-05-25 06:56:01 Re: pg_class reltuples/relpages not updated by autovacuum/vacuum
Previous Message Fujii Masao 2011-05-25 01:59:01 Re: Seems like a large amount of xlog files

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2011-05-25 02:52:41 Re: tackling full page writes
Previous Message Josh Kupershmidt 2011-05-25 02:31:50 Re: patch: Allow \dd to show constraint comments