Tom Lane wrote:
> David Scott <davids@apptechsys.com> writes:
>
>> Is the additional overhead of keeping full tuple visibility
>>information inside of the index so odious to the Postgres community as
>>to prevent a patch with this solution from being applied back to the
>>head?
>
> This has been discussed and rejected before (multiple times). If you
> want it considered you'll have to present stronger arguments than have
> so far been made. The current consensus is that the probability of a
> net performance win is not good enough to justify the large amount of
> development effort that would be required.
What ever happened to grouped heap reads, i.e. building a list of tuples
from the index, sorting in heap order, then reading the heap in a batch?
The last I remember (maybe two years ago), it was being discussed but
no design decisions had been made. Is that what you're talking about?
-Glen
