X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D07169FA5E6 for ; Sun, 18 Jun 2006 05:46:06 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 62482-02 for ; Sun, 18 Jun 2006 05:45:58 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.226]) by postgresql.org (Postfix) with ESMTP id D8D4B9F9AD3 for ; Sun, 18 Jun 2006 05:45:58 -0300 (ADT) Received: by wr-out-0506.google.com with SMTP id i12so791761wra for ; Sun, 18 Jun 2006 01:45:57 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=XSnWyhAq7FPy8VGAXOe0HY1pAXwsSobLgu+m42dJNbIDldJTiJaGtvvWKgmYXaOOxtl8xlhL+XckufOlnSarLC3Q4mADq8zaEmURiGR0HiNX779VUh6V5qHW0zhPG16iu58ja/Ush5cKzBEITcnVA0X5YZIMs1b7f6b24yHLWEg= Received: by 10.65.185.16 with SMTP id m16mr3303088qbp; Sun, 18 Jun 2006 01:45:57 -0700 (PDT) Received: by 10.65.185.5 with HTTP; Sun, 18 Jun 2006 01:45:57 -0700 (PDT) Message-ID: <5d141cb10606180145y2d1b8f18m8d855aa77fbbd05d@mail.gmail.com> Date: Sun, 18 Jun 2006 14:15:57 +0530 From: "Ravindra Guravannavar" To: pgsql-admin@postgresql.org Subject: clustering takes too long! Cc: ravindrag@gmail.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_105421_1836011.1150620357510" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/181 X-Sequence-Number: 22143 ------=_Part_105421_1836011.1150620357510 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, I am trying to cluster an index on the TPC-H lineitem table having 6 million records. The index is on a single column l_suppkey. Postgres (8.1.3) is not able to finish the operation even after 2 hours! The disk is being accessed continuously and CPU is at 2%. Postmaster is started with the following options: -B 2000 --work-mem=10240 --maintenance_work_mem=10240 --wal_buffers=32 --checkpoint_segments=128 --checkpoint_timeout=600 No useful messages in the logfile. With the default checkpoint_segments (before I increased it to 128), there was a warning about checkpoints taking place too frequently. I tried this on two different machines and also with 8.1.4 and see the same behavior. On the same system, I am able to cluster an index on another much larger table (10 million) records within few minutes. Any clues on what could be going wrong? Thanks, Ravi ------=_Part_105421_1836011.1150620357510 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi,

I am trying to cluster an index on the TPC-H lineitem table having
6 million records. The index is on a single column l_suppkey.  Postgres
(8.1.3) is not able to finish the operation even after 2 hours! The disk
is being accessed continuously and CPU is at 2%. Postmaster is
started with the following options:

-B 2000 --work-mem=10240 --maintenance_work_mem=10240 --wal_buffers=32 --checkpoint_segments=128 --checkpoint_timeout=600

No useful messages in the logfile. With the default checkpoint_segments
(before I increased it to 128), there was a warning about checkpoints taking
place too frequently.

I tried this on two different machines and also with 8.1.4 and see the
same behavior.

On the same system, I am able to cluster an index on another much
larger table (10 million) records within few minutes.

Any clues on what could be going wrong?

Thanks,
Ravi

------=_Part_105421_1836011.1150620357510--