| From: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
|---|---|
| To: | Hfe80 <federico(dot)mo(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: DB become enormous with continuos insert and update |
| Date: | 2010-10-26 22:12:09 |
| Message-ID: | AANLkTinYp-j+X+3-A8G4NZu688_+qbP=tfADKkrhq1hx@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 26 October 2010 22:01, Hfe80 <federico(dot)mo(at)gmail(dot)com> 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?
>
This article describes why you should almost never use vacuum full:
http://it.toolbox.com/blogs/database-soup/getting-rid-of-vacuum-full-feedback-needed-33959
You need to vacuum more aggressively.
--
Regards,
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hfe80 | 2010-10-26 22:22:20 | Re: DB become enormous with continuos insert and update |
| Previous Message | John R Pierce | 2010-10-26 21:55:53 | Re: DB become enormous with continuos insert and update |