| From: | decibel <decibel(at)decibel(dot)org> |
|---|---|
| To: | decibel <decibel(at)decibel(dot)org> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow vacuumdb to only analyze |
| Date: | 2009-05-29 23:44:46 |
| Message-ID: | 49593C6F-0A72-4E50-9502-44F8ED1F59DE@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 27, 2009, at 11:31 AM, decibel wrote:
>> It does seem somewhat useful to be able to analyze all databases
>> easily from the command-line, but putting it into vacuumdb is
>> certainly a hack.
> So... do we want a completely separate analyzedb command? That
> seems like far overkill.
>
> Arguably there are yet other things you'd want to do across an
> entire cluster, so perhaps what we really want is a 'clusterrun' or
> 'clustercmd' command?
No one else has commented, so I'm guessing that means no one is
opposed to allowing for vacuumdb to just analyze. If anyone else
objects to this please speak up before I put the final touches on the
patch...
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-05-29 23:53:14 | Re: search_path vs extensions |
| Previous Message | James Pye | 2009-05-29 22:43:05 | Re: Python 3.0 does not work with PL/Python |