| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Bill Chandler <billybobc1210(at)yahoo(dot)com> |
| Cc: | pgsql-perform <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Question on vacuumdb |
| Date: | 2005-04-18 19:58:19 |
| Message-ID: | 20050418195819.GB4961@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Apr 18, 2005 at 12:27:08 -0700,
Bill Chandler <billybobc1210(at)yahoo(dot)com> wrote:
> All,
>
> If I run the command "vacuumdb mydb" I understand that
> it does some disk space recovery (but not as much as
> "vacuumdb --full mydb").
You are better off not using vacuum full unless some unusual event has
bloated your database. By running normal vacuums often enough (and with
a large enough fsm setting) your database should reach a steady state size.
> Question: if I run the command "vacuumdb --analyze
> mydb" does it still do the aforementioned disk space
> recovery AS WELL AS update query planning statistics?
> Or are those two completely separate operations
> requiring separate invocations of 'vacuumdb'.
It is better to do both with one command.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-04-18 20:13:54 | Re: Question on REINDEX |
| Previous Message | Bruno Wolff III | 2005-04-18 19:53:58 | Re: Question on REINDEX |