From: | Chantal Ackermann <chantal(dot)ackermann(at)biomax(dot)de> |
---|---|
To: | shridhar_daithankar(at)persistent(dot)co(dot)in, tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: unused tuples constantly increasing |
Date: | 2003-01-10 15:49:03 |
Message-ID: | 3E1EEB6F.9040204@biomax.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
hello Shridhar, hello Tom,
long story short:
Neither adding ANALYZE nor reducing the rows from 2000 at one time to
500 changes anything: the UnUsed value keeps growing, as does the
overall amount of pages. The VACUUM ANALYZE takes the same time or even
more.
Following your advice, Tom, I increased the rows to 200,000. The update
now takes about 140 secs, the VACUUM ANALYZE more than 200 secs. The
amount of pages increases a lot, as does UnUsed. Moreover, the
transaction log files get recycled a lot - which did not happen with
2000 rows at one time. But nevertheless - with 200000 rows at one time
there are only few cycles untill all 2 million rows are updated, so in
the end this should be the faster way.
thank you for your help!
Chantal
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2003-01-10 16:23:53 | persistant transactions |
Previous Message | Robert Treat | 2003-01-10 15:36:05 | Re: Stable function Repeatedly Called |