| From: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Performance problems |
| Date: | 2003-04-25 15:08:20 |
| Message-ID: | 200304252038.20751.shridhar_daithankar@nospam.persistent.co.in |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday 25 April 2003 20:23, marco wrote:
> I unfortunately don't understand the whole thing totally, but if I dump
> the database (with pg_dump), delete it and restore it, the time values
> for reading and writing have decreased to a normal level and begin to
> increase again.
>
> It seems to me, that I do sth. fundamentally wrong :( But even after
> searching google and the postgresql archives I don't see the light at
> all...
You need to vacuum full everytime you delete large amount of rows and vacuum
analyze every time you insert/update large amount of rows..
I would say large amount==50K row is a good start.. So after 20 runs of tool,
run vacuum once.. Try it and let us know..
Shridhar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Gearon | 2003-04-25 15:13:32 | Re: Performance problems |
| Previous Message | Manuel Durán Aguete | 2003-04-25 15:05:59 | Re: Performance problems |