vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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"). 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'. thanks, Bill __________________________________ Do you Yahoo!? Plan great trips with Yahoo! Travel: Now over 17,000 guides! http://travel.yahoo.com/p-travelguide ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq |
| ||||
| On Mon, Apr 18, 2005 at 12:27:08 -0700, Bill Chandler <billybobc1210@yahoo.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. ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |