Re: Found a bug

Thanks for the references.

Note for future: should have tried VACUUM too.

On 11/7/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> writes:
> > Please refer the following session snippet. It seems that creating
> and
> > dropping an index on a table, within a transaction, leaves the table
> marked
> > as having an index.
>
> This isn't a bug. Refer to catalogs.sgml:
>
> relhasindex
> True if this is a table and it has (or recently had) any indexes.
> This is set by CREATE INDEX, but not cleared immediately by DROP
> INDEX. VACUUM clears relhasindex if it finds the table has no
> indexes.
>
> The flag is only used as a hint that it's worth looking in pg_index to
> see what rows there are for the table.
>
> As for "tracking it down", read index_drop().
>
> regards, tom lane
>

--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | yahoo }.com