BUG #4410: Indexes not seen right away - Mailing list pgsql-bugs

From Greg Sabino Mullane
Subject BUG #4410: Indexes not seen right away
Date
Msg-id 200809072104.m87L43IA061113@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #4410: Indexes not seen right away
List pgsql-bugs
The following bug has been logged online:

Bug reference:      4410
Logged by:          Greg Sabino Mullane
Email address:      greg@endpoint.com
PostgreSQL version: 8.3.3
Operating system:   Linux
Description:        Indexes not seen right away
Details:

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. Creating a second table based on the first worked as it
should during the 'noindex' time period: CREATE TABLE foo AS SELECT * FROM
bar; CREATE INDEX foo_idx1 ON foo(textcol); EXPLAIN SELECT 1 FROM foo WHERE
textcol1 = 'baz';

pgsql-bugs by date:

Previous
From: "prasana venkatesh"
Date:
Subject: BUG #4409: postmaster service is stopped
Next
From: Tom Lane
Date:
Subject: Re: BUG #4410: Indexes not seen right away