currentItemData & currentMarkData - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject currentItemData & currentMarkData
Date
Msg-id 4506BDC0.2050705@enterprisedb.com
Whole thread Raw
Responses Re: currentItemData & currentMarkData  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
It has bothered me for some time that we have currentItemData and 
currentMarkData fields in IndexScanDescData, while it's really indexam's 
private data. They should be in the indexam opaque structure.

At the moment, they're used in gist and hash access methods, and they're 
not used in b-tree and gin. The new bitmap index code uses them, but 
only as an internal boolean flag indicating that the scan has been 
initialized, so that should be fixed anyway.

How about removing those fields from IndexScanDesc?

There's also is_multiscan field which is set but never read.

-- 
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: AIX shared libraries (was Re: [PATCHES] Fix linking of OpenLDAP libraries)
Next
From: Tom Lane
Date:
Subject: Re: Bitmap index status