Re: Additional stats for Relations

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: NikhilS <nikkhils(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Additional stats for Relations
Date: 2006-10-19 15:08:38
Message-ID: 20061019150838.GS71084@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 19, 2006 at 04:10:46PM +0530, NikhilS wrote:
> Hi Jim,
>
> On 10/18/06, Jim C. Nasby <jim(at)nasby(dot)net> wrote:
> >
> >Also how many times a relation has been vacuumed (which puts all the
> >other numbers in more perspective... good catch Simon). And I think
> >number of pages that could not be added to the FSM would also be
> >extremely valuable.
>
>
> By the above, do you mean the number of pages that could not be added to the
> FSM because they had freespace which was less than the threshold for this
> particular relation?

Yes... but... :)

We want to ignore pages that have less than the average request size,
because vacuum will never try and put them in the FSM anyway. We only
care about pages that were dropped because MaxFSMPages was less than
DesiredFSMPages (see freespace.c for more info).

It would also be useful to keep track of what relations have been bumped
out of the FSM (or never got recorded, though I'm not sure if that's
possible) because we've run into the MaxFSMRelations limit.

BTW, if we add these counters we'll be up to 7 stats dealing with vacuum
and analyze, and NikhilS has a patch we're finalizing that would add 3
more. Right now there's 4 slated to go into pg_stat_* in 8.2, but maybe
we should have a separate view for vacuum/FSM statistics?
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message tomas 2006-10-19 15:18:44 Re: Statements with syntax errors are not logged
Previous Message Peter Eisentraut 2006-10-19 15:03:08 Re: Statements with syntax errors are not logged