Thanks for the references.Note for future: should have tried VACUUM too.On 11/7/06, Tom Lane <[EMAIL PROTECTED]
> wrote:"Gurjeet Singh" <
[EMAIL PROTECTED]> writes:> Please refer the following session snippet. It seems that creating and> dropping an index on a table, within a transaction, leave
"Gurjeet Singh" <[EMAIL PROTECTED]> 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
Gurjeet Singh wrote:
Hi All,
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. Although, I don't think it's a serious bug, since we
always retrieve the list using RelationGetIn
Hi All, 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. Although, I don't think it's a serious bug, since we always retrieve the list using RelationGetIndexList(), and that list
