Vacuum runs in a loop?

From: Wim <wdh(at)belbone(dot)be>
To: pgsql-novice(at)postgresql(dot)org
Subject: Vacuum runs in a loop?
Date: 2003-09-15 17:26:05
Message-ID: 1063646764.17554.24.camel@tyr.car.belbone.be
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Hi all,

I have a question:
I deleted half of the records in my table and to free up the space I do
a VACUUM VERBOSE.
Is it normal that my VACUUM VERBOSE runs in a loop?
If not, what can I do to free up disk space?

INFO: Index i_flowdata_dst_as: Pages 171123; Tuples 23875181: Deleted
0.
CPU 10.78s/14.52u sec elapsed 831.52 sec.
INFO: Index i_flowdata_end_time: Pages 226712; Tuples 23875181: Deleted
0.
CPU 13.96s/14.66u sec elapsed 496.71 sec.
INFO: Index i_flowdata_src_as: Pages 171170; Tuples 23875181: Deleted
0.
CPU 10.30s/14.02u sec elapsed 817.77 sec.
INFO: Index i_flowdata_start_time: Pages 213650; Tuples 23875181:
Deleted 0.
CPU 12.00s/14.83u sec elapsed 478.88 sec.
INFO: Removed 1397825 tuples in 21505 pages.
CPU 2.36s/2.65u sec elapsed 73.53 sec.
INFO: Index i_flowdata_dst_as: Pages 171123; Tuples 23875181: Deleted
0.
CPU 10.35s/14.19u sec elapsed 834.93 sec.
INFO: Index i_flowdata_end_time: Pages 226712; Tuples 23875181: Deleted
0.
CPU 13.66s/14.35u sec elapsed 490.73 sec.
INFO: Index i_flowdata_src_as: Pages 171170; Tuples 23875181: Deleted
0.
CPU 11.05s/14.13u sec elapsed 820.02 sec.
INFO: Index i_flowdata_start_time: Pages 213650; Tuples 23875181:
Deleted 0.
CPU 12.58s/14.39u sec elapsed 472.55 sec.
INFO: Removed 1397825 tuples in 21505 pages.
CPU 2.39s/2.28u sec elapsed 63.14 sec.

INFO: Index i_flowdata_dst_as: Pages 171123; Tuples 23875181: Deleted
0.
CPU 10.68s/14.19u sec elapsed 830.23 sec.
INFO: Index i_flowdata_end_time: Pages 226712; Tuples 23875181: Deleted
0.
CPU 13.89s/14.41u sec elapsed 490.14 sec.
INFO: Index i_flowdata_src_as: Pages 171170; Tuples 23875181: Deleted
0.
CPU 10.17s/14.42u sec elapsed 826.22 sec.
INFO: Index i_flowdata_start_time: Pages 213650; Tuples 23875181:
Deleted 0.
CPU 11.76s/14.61u sec elapsed 580.53 sec.
INFO: Removed 1397825 tuples in 21505 pages.
CPU 2.29s/2.26u sec elapsed 92.32 sec.
INFO: Index i_flowdata_dst_as: Pages 171123; Tuples 23875181: Deleted
0.
CPU 11.00s/14.56u sec elapsed 1374.93 sec.
INFO: Index i_flowdata_end_time: Pages 226712; Tuples 23875181: Deleted
0.
CPU 15.37s/15.35u sec elapsed 785.42 sec.
INFO: Index i_flowdata_src_as: Pages 171170; Tuples 23875181: Deleted
0.
CPU 10.30s/14.37u sec elapsed 1278.69 sec.
INFO: Index i_flowdata_start_time: Pages 213650; Tuples 23875181:
Deleted 0.
CPU 12.78s/13.93u sec elapsed 479.11 sec.
INFO: Removed 1397825 tuples in 21505 pages.
CPU 2.64s/2.16u sec elapsed 72.25 sec.
INFO: Index i_flowdata_dst_as: Pages 171123; Tuples 23875181: Deleted
0.
CPU 10.30s/13.68u sec elapsed 835.70 sec.
INFO: Index i_flowdata_end_time: Pages 226712; Tuples 23875181: Deleted
0.
CPU 13.63s/14.41u sec elapsed 493.88 sec.
INFO: Index i_flowdata_src_as: Pages 171170; Tuples 23875181: Deleted
0.
CPU 10.59s/14.19u sec elapsed 826.78 sec.
INFO: Index i_flowdata_start_time: Pages 213650; Tuples 23875181:
Deleted 0.
CPU 12.90s/14.34u sec elapsed 478.05 sec.
INFO: Removed 1397825 tuples in 21505 pages.
CPU 2.31s/2.31u sec elapsed 63.51 sec.

Cheers!
Wim De Hul
------------------------------------------------------------------------------
IP SERVICES SPECIALIST
Belgacom Carrier and Wholesale Business Unit (CBU)
------------------------------------------------------------------------------
AS6774
Ripe : WDH25-RIPE
reply-to : NOC{at}belbone{dot}be
peering : peering{at}belbone{dot}be
NOC Tel : +32 2/547.51.00
www.belgacom.be/carrier
------------------------------------------------------------------------------
------------------------------------------------------------------------------
7:23pm up 6 days, 7:09, 1 user, load average: 1.30, 1.57, 1.56

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Max Nachlinger 2003-09-15 17:30:53 recursive call to function returning SETOF
Previous Message szucs 2003-09-15 15:07:40 Re: Search for data in a similar field in a related table, too