Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 07DDE64FCED for ; Sun, 7 Sep 2008 18:18:42 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 83312-04 for ; Sun, 7 Sep 2008 18:18:39 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id E551364FCE1 for ; Sun, 7 Sep 2008 18:18:38 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m87LIVHn016774; Sun, 7 Sep 2008 17:18:31 -0400 (EDT) To: "Greg Sabino Mullane" cc: pgsql-bugs@postgresql.org Subject: Re: BUG #4410: Indexes not seen right away In-reply-to: <200809072104.m87L43IA061113@wwwmaster.postgresql.org> References: <200809072104.m87L43IA061113@wwwmaster.postgresql.org> Comments: In-reply-to "Greg Sabino Mullane" message dated "Sun, 07 Sep 2008 21:04:03 +0000" Date: Sun, 07 Sep 2008 17:18:31 -0400 Message-ID: <16773.1220822311@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/62 X-Sequence-Number: 21352 "Greg Sabino Mullane" writes: > I cannot reproduce, as this was on a production system and not seen again, > but I created a simple index on a TEXT field, which was not chosen by the > planner, even when seqscan was turned off. I analyzed the table, checked all > the settings, etc. pg_index looked as it should. Eventually (~ 10 minutes > later) the index as chosen - I don't know what might have triggered it to > start appearing. Does it have pg_index.indcheckxmin = true? If so, see README.HOT. regards, tom lane