Re: COUNT(*) and index-only scans - Mailing list pgsql-hackers

From Greg Stark
Subject Re: COUNT(*) and index-only scans
Date
Msg-id CAM-w4HNpbKyqFMmH3ZahRTP_htK+42OGMbjMpY7ur30xSSKbCg@mail.gmail.com
Whole thread Raw
In response to Re: COUNT(*) and index-only scans  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: COUNT(*) and index-only scans  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Mon, Nov 21, 2011 at 6:43 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> In buffer fill mode, we scan the index and add matching tuples and
> their CTIDs to the buffer.  When the buffer is full or the index AM
> reports that there are no more tuples in the scan, we switch to buffer
> drain mode.

Instead you could do the two phases concurrently the way tuplesort
implements the tapesort from Knuth. You keep a heap of ctids with an
epoch. You fill the heap then you return the first one. Whenever you
return one you read the next one and add it to the heap. If it falls
before the last returned value you insert it with the next epoch but
if it falls afterwards you can insert it into the heap in its correct
position.




--
greg


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: pg_dump --exclude-table-data
Next
From: Pavan Deolasee
Date:
Subject: Re: Race condition in HEAD, possibly due to PGPROC splitup