X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2CADA329E23 for ; Mon, 27 Sep 2004 17:32:41 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 45564-01 for ; Mon, 27 Sep 2004 16:32:33 +0000 (GMT) Received: from mail.musicrebellion.com (dsl093-203-229.ind1.dsl.speakeasy.net [66.93.203.229]) by svr1.postgresql.org (Postfix) with ESMTP id 153AE329CAE for ; Mon, 27 Sep 2004 17:32:32 +0100 (BST) Received: from [10.0.1.102] (helo=musicrebellion.com ident=kris) by mail.musicrebellion.com with asmtp (Exim 4.34 #1 (Debian)) id 1CByQP-0007ke-2c for ; Mon, 27 Sep 2004 11:32:29 -0500 Message-ID: <4158409E.8060109@musicrebellion.com> Date: Mon, 27 Sep 2004 11:32:30 -0500 From: Kris Kiger User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 X-Accept-Language: en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: tsearch2 poor performance References: <71E37EF6B7DCC1499CEA0316A2568328DC9DF0@loki.wc.globexplorer.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/249 X-Sequence-Number: 14952 Regardless of caching, the queries are still taking 19~20 seconds to run on the 3,000,000 rows. I've played with performance tuning and nothing seems to make much of a difference. If I am reading that list from stat correctly, then I am operating on 508 distinct words. Is this the performance I should expect from tsearch2? Or is something still awry? I'm inclined to think something else is wrong, after reading some other people's tsearch performance stats. Thanks! Kris