X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E29B5D1EF33 for ; Mon, 3 May 2004 11:53:17 -0300 (ADT) 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 95380-04 for ; Mon, 3 May 2004 11:53:01 -0300 (ADT) Received: from localhost.localdomain (66.239.202.254.ptr.us.xo.net [66.239.202.254]) by svr1.postgresql.org (Postfix) with ESMTP id 95A81D1EF1B for ; Mon, 3 May 2004 11:52:56 -0300 (ADT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.11.6/8.11.6) with ESMTP id i43AtOs28074 for ; Mon, 3 May 2004 10:55:24 GMT Subject: an indexing problem on postgreSQL From: jwang To: pgsql-sql@postgresql.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 03 May 2004 10:55:23 +0000 Message-Id: <1083581724.24056.14.camel@localhost> Mime-Version: 1.0 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/24 X-Sequence-Number: 17738 All, I have an data-driven web application with Java and PostgreSQL. We have a few tables which hold quite large amount of data. Therefore we put indexing (B-tree) on them to make query faster. In addition, we are also doing data synchronization on these tables with another microsoft FoxPro application in real-time. Normally the indexing works just fine without data synchronization. But with data synchronization, after a period of time, the indexing did not take effect on the table so that the application goes extremely slow. Does anyone there has an idea why and have a solution to the problem? Your help is greatly appreciated. Sincerely, -John