Re: currentItemData & currentMarkData

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: currentItemData & currentMarkData
Date: 2006-09-12 14:59:34
Message-ID: 16246.1158073174@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> 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.

Can't get very excited about it, but if you want.

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

It has been needed in the past and could plausibly be needed again
sometime --- an index AM's rescan method might want to know what kind
of scan it's setting up for. Of course, if we get rid of amgetmulti
entirely as has been discussed, this'd go away too.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2006-09-12 15:18:08 Re: dump / restore functionality
Previous Message Tom Lane 2006-09-12 14:40:42 Re: dump / restore functionality