Re: Double entries in log for page slots in beta3

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jim Nasby <decibel(at)decibel(dot)org>, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Double entries in log for page slots in beta3
Date: 2006-12-05 21:26:59
Message-ID: 20061205212659.GJ44124@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 05, 2006 at 11:04:17AM -0500, Tom Lane wrote:
> Jim Nasby <decibel(at)decibel(dot)org> writes:
> > AFAIK there isn't, and it would be useful to have. But FSM info alone
> > doesn't tell you the whole picture; you'd have to know that vacuum
> > couldn't find space in the FSM to store some pages. So perhaps what's
> > really needed is information about how many pages in a relation
> > couldn't be put into the FSM the last time a vacuum was run.
>
> Curiously enough, that's exactly what the FSM stats tell you now.

But only at the end of a database-wide vacuum verbose, right? Or did I
miss something?

It would be useful to be able to get that info in a system running
autovac (or anything else that means not normally vacuuming the whole
database).
--
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 Tom Lane 2006-12-05 21:32:40 Re: psql possible TODO
Previous Message Tom Lane 2006-12-05 21:24:52 Re: [HACKERS] Configuring BLCKSZ and XLOGSEGSZ (in 8.3)