Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id B20C62E02D6 for ; Sun, 9 Dec 2007 06:46:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 93255-07 for ; Sun, 9 Dec 2007 06:42:39 -0400 (AST) Received: from smtp8-g19.free.fr (smtp8-g19.free.fr [212.27.42.65]) by postgresql.org (Postfix) with ESMTP id 801DF2E0118 for ; Sun, 9 Dec 2007 06:42:42 -0400 (AST) Received: from smtp8-g19.free.fr (localhost [127.0.0.1]) by smtp8-g19.free.fr (Postfix) with ESMTP id 5169117F574 for ; Sun, 9 Dec 2007 11:42:40 +0100 (CET) Received: from zoot.local (tru75-6-82-240-32-109.fbx.proxad.net [82.240.32.109]) by smtp8-g19.free.fr (Postfix) with ESMTP id 3648317F53A for ; Sun, 9 Dec 2007 11:42:40 +0100 (CET) From: =?utf-8?q?Herv=C3=A9_Piedvache?= To: pgsql-performance@postgresql.org Subject: Vacuum full since 15 hours Date: Sun, 9 Dec 2007 11:42:41 +0100 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) X-Face: Q~R=,(z%>18cais1AC25|#(q>ihP; 4[0^5ZM!|rrF`; J\cq%{ei$`jaEfrxkS9NtP{X'KUd]\gZGcj3#r|*.[; @'w}feV"=?utf-8?q?=607=607j=60=7E=0A=09f7=7EF?=){$[oAPG)?M2ro}dZKHoYd8P?1JTUr$>6@G0yQV9Y\FNpONS+i.Y1M{=eAFuJo6.}6d-k:zp+_*@/mec@(<=?utf-8?q?=5B=26*aFBsp*FRX8=24=0A=09=27czo-6h=23kce+f?=(Z?KlRecYCEEb,vA{Lq MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200712091142.41651.bill.footcow@gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/110 X-Sequence-Number: 27926 Hi, I have a small question ... right now on a 8.1.10 version of PostgreSQL I'm= =20 doing a vacuum full verbose anaylze a table with 60 304 340 rows in 115579= 1=20 pages and there were 16 835 144 unused item pointers inside and 5 index. After the first treatment of the index (appeared in the verbose) ... the=20 vacuum is still working now since 15 hours ... There is none other activity= =20 on this server ... it's a replication server ... so the vacuum is locking=20 most of the replication queries ... What can I do to get this doing quicker ...? It's a 8Gb server ... with a RAID 10 ... my maintenance_work_mem =3D 25600. Any idea ? I'm sure that if I delete all the index an rebuild them by hand it'll be=20 really quicker ! (done on another replication server ... took 20 min) regards, =2D-=20 Herv=C3=A9 Piedvache