Re: Autovacuum on by default?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Larry Rosenman <ler(at)lerctr(dot)org>, "'Jim C(dot) Nasby'" <jim(at)nasby(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Autovacuum on by default?
Date: 2006-08-24 17:48:50
Message-ID: 20060824174850.GC20829@alvh.no-ip.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> "Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> > On Thu, Aug 24, 2006 at 09:58:10AM -0400, Tom Lane wrote:
> >> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> >>> I think there is a reasonable case for saying that a manual vacuum could
> >>> hint pgstat to create the entry instead.
> >>
> >> The problem with that is that a simple "VACUUM;" would force pgstat to
> >> populate its entire hashtable.
>
> > Maybe a good compromise would be only populating info for tables that
> > had dead tuples... that would eliminate any static tables, and most DBAs
> > should know that those tables are static.
>
> Hm, that definitely seems like an idea. Does the current pgstat message
> from vacuum tell how many rows it deleted?

Hum, no.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message AgentM 2006-08-24 17:48:52 Re: tsvector/tsearch equality and/or portability issue issue ?
Previous Message Teodor Sigaev 2006-08-24 17:40:13 Re: tsvector/tsearch equality and/or portability issue