"Greg Sabino Mullane" <greg@endpoint.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
