X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 3CC0CD1D17D for ; Fri, 2 Jan 2004 22:29:24 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 65516-02 for ; Fri, 2 Jan 2004 18:28:40 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id A403CD1DE41 for ; Fri, 2 Jan 2004 18:16:12 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i02FpD19005931; Fri, 2 Jan 2004 10:51:13 -0500 (EST) To: =?iso-8859-15?q?Herv=E9=20Piedvache?= Cc: pgsql-performance@postgresql.org Subject: Re: Why memory is not used ? Why vacuum so slow ? In-reply-to: <200401021618.28300.herve@elma.fr> References: <200401021042.57714.herve@elma.fr> <5630.1073054548@sss.pgh.pa.us> <200401021618.28300.herve@elma.fr> Comments: In-reply-to =?iso-8859-15?q?Herv=E9=20Piedvache?= message dated "Fri, 02 Jan 2004 16:18:28 +0100" Date: Fri, 02 Jan 2004 10:51:13 -0500 Message-ID: <5930.1073058673@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/9 X-Sequence-Number: 5184 =?iso-8859-15?q?Herv=E9=20Piedvache?= writes: > and I have also saw that the full vacuum for pg_atribute seems > to be so slow ... more than 1 min for 7256 tupples ? Is this is normal ? > INFO: --Relation pg_catalog.pg_attribute-- > INFO: Pages 119: Changed 0, reaped 1, Empty 0, New 0; Tup 7256: Vac 0, Keep/ > VTL 0/0, UnUsed 3, MinLen 128, MaxLen 128; Re-using: Free/Avail. Space > 14664/504; EndEmpty/Avail. Pages 0/1. > CPU 0.00s/0.00u sec elapsed 0.08 sec. > INFO: Index pg_attribute_relid_attnam_index: Pages 21082; Tuples 7256: > Deleted 0. > CPU 0.83s/0.13u sec elapsed 59.32 sec. > INFO: Index pg_attribute_relid_attnum_index: Pages 5147; Tuples 7256: Deleted > 0. > CPU 0.26s/0.03u sec elapsed 8.79 sec. You're suffering from index bloat (21000 pages in an index for a 119-page table!?). Updating to 7.4 would probably fix this, but if that's not practical consider reindexing pg_attribute. regards, tom lane