From: | "Greg Sabino Mullane" <greg(at)endpoint(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #4410: Indexes not seen right away |
Date: | 2008-09-07 21:04:03 |
Message-ID: | 200809072104.m87L43IA061113@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-docs |
The following bug has been logged online:
Bug reference: 4410
Logged by: Greg Sabino Mullane
Email address: greg(at)endpoint(dot)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';
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-09-07 21:18:31 | Re: BUG #4410: Indexes not seen right away |
Previous Message | prasana venkatesh | 2008-09-07 16:26:37 | BUG #4409: postmaster service is stopped |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-09-07 21:18:31 | Re: BUG #4410: Indexes not seen right away |
Previous Message | Bruce Momjian | 2008-09-07 12:31:48 | Re: Incorrect description of xmax and xip in functions docs |