From: | "Peter Bauer" <peter(dot)m(dot)bauer(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Overload after some minutes, please help! |
Date: | 2006-10-19 15:33:20 |
Message-ID: | 764c9e910610190833y6b1da453ud6f81e21dde963f0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
thank you, so we will perform the tests with such a vacuum configuration,
br,
Peter
2006/10/19, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> "Peter Bauer" <peter(dot)m(dot)bauer(at)gmail(dot)com> writes:
> > There is a table called tableregistrations where per day about
> > 1 million rows are INSERTed
> > 20000 SELECTs should be performed on it
> > 10000 UPDATEs should be performed where about 100 rows are updated
> > with each execution
> > 10000 DELETEs should be performed every 10 seconds
> > in such a way that the table constantly contains about 20000 entries.
>
> > A vaccum of the whole database is performed every 10 minutes with
> > cron, autovacuum is enabled too.
>
> That's not *nearly* enough given that level of row turnover. You need
> to be vacuuming that table about once a minute if not more often, and
> you need to be sure that there aren't any long-running transactions that
> would prevent vacuum from removing dead rows.
>
> Try a VACUUM VERBOSE after the system has gotten into a slow state to
> get more info about exactly what's happening.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | James Cradock | 2006-10-19 15:35:44 | Re: PostGIS |
Previous Message | Peter Bauer | 2006-10-19 15:31:45 | Re: Overload after some minutes, please help! |