Re: BUG #4410: Indexes not seen right away

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Greg Sabino Mullane" <greg(at)endpoint(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4410: Indexes not seen right away
Date: 2008-09-07 21:18:31
Message-ID: 16773.1220822311@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-docs

"Greg Sabino Mullane" <greg(at)endpoint(dot)com> 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2008-09-07 23:58:06 Re: non-deterministic error related to MIN/MAX optimization
Previous Message Greg Sabino Mullane 2008-09-07 21:04:03 BUG #4410: Indexes not seen right away

Browse pgsql-docs by date

  From Date Subject
Next Message Simon Riggs 2008-09-08 06:56:35 Re: Incorrect description of xmax and xip in functions docs
Previous Message Greg Sabino Mullane 2008-09-07 21:04:03 BUG #4410: Indexes not seen right away