On Tue, 2010-10-26 at 14:01 -0700, Hfe80 wrote: > Some one know how to solve the problem of db that became huge from 700 Mbyte > to 16 Gbyte in 10 days and grow... > Vacuum doesn't solve the problem. > Only vacuum full is too invasive, the only way to reduce the DB is dump and > restore, but we cannot stop service... > > I know that a in a similar db where there is a lot of update the problem was > solved but I don't know how... > Some one Know this problem?
You are not vacuuming enough. If you vacuuum more often you should be able to keep bloat down. Joshua D. Drake > > Thank's :) > -- > View this message in context: > http://postgresql.1045698.n5.nabble.com/DB-become-enormous-with-continuos-insert-and-update-tp3237814p3237814.html > Sent from the PostgreSQL - general mailing list archive at Nabble.com. > -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579 Consulting, Training, Support, Custom Development, Engineering http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
