Greg Sabino Mullane wrote:
>
Does it have pg_index.indcheckxmin = true? If so, see README.HOT.
>>> Yes, that was probably it. Is this worth noting in the documentation
>>> somewhere
>>> (other than the technical bowels of HOT)? Perhaps in the CREATE INDEX
>>> docs?
> ...
>> I have attached
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> > > Does it have pg_index.indcheckxmin = true? If so, see README.HOT.
>
>> Yes, that was probably it. Is this worth noting in the documentation
>> somewhere
>> (other than the technical bowels of HOT)? Perhaps in the CREATE INDEX
>> docs?
..
Greg Sabino Mullane wrote:
> > Does it have pg_index.indcheckxmin = true? If so, see README.HOT.
>
> Yes, that was probably it. Is this worth noting in the documentation somewhere
> (other than the technical bowels of HOT)? Perhaps in the CREATE INDEX
> docs?
I have done some research on this.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Does it have pg_index.indcheckxmin = true? If so, see README.HOT.
Yes, that was probably it. Is this worth noting in the documentation somewhere
(other than the technical bowels of HOT)? Perhaps in the CREATE INDEX
docs?
- --
Greg Sabino Mu
"Greg Sabino Mullane" <[EMAIL PROTECTED]> 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, e
The following bug has been logged online:
Bug reference: 4410
Logged by: Greg Sabino Mullane
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Linux
Description:Indexes not seen right away
Details:
I cannot reproduce, as this was on a prod
