Skip site navigation (1) Skip section navigation (2)

Re: Allow vacuumdb to only analyze

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: decibel <decibel(at)decibel(dot)org>
Cc: "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allow vacuumdb to only analyze
Date: 2010-02-25 22:09:11
Message-ID: 201002252209.o1PM9B706481@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
decibel wrote:
> One of the talks at PGCon (update in place?) recommended running  
> vacuumdb -z to analyze all tables to rebuild statistics. Problem with  
> that is it also vacuums everything. ISTM it'd be useful to be able to  
> just vacuum all databases in a cluster, so I hacked it into vacuumdb.
> 
> Of course, using a command called vacuumdb is rather silly, but I  
> don't see a reasonable way to deal with that. I did change the name  
> of the functions from vacuum_* to process_*, since they can vacuum  
> and/or analyze.
> 
> The only thing I see missing is the checks for invalid combinations  
> of options, which I'm thinking should go in the function rather than  
> in the option parsing section. But I didn't want to put any more  
> effort into this if it's not something we actually want.

This is implemented in 9.0 from vacuumdb:

	  -Z, --analyze-only              only update optimizer hints

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com
  PG East:  http://www.enterprisedb.com/community/nav-pg-east-2010.do
  + If your life is a hard drive, Christ can be your backup. +

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-02-25 22:11:11
Subject: Re: feature request
Previous:From: Robert HaasDate: 2010-02-25 22:07:58
Subject: Re: A thought: should we run pgindent now?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group