On Mon, Oct 6, 2014 at 11:27 AM, Robert Haas <robertmh...@gmail.com> wrote: > Well, really, I was just suggesting that I can spend more time on the > patch, but not immediately.
We haven't really talked about the idea of the HyperLogLog-based abort mechanism - the actual cost model - even though I thought we'd have discussed that extensively by now. Maybe I'm reading too much into that, but my guess is that that's because it's a particularly hard thing to have an opinion on. I think that It might not be a bad idea to have another opinion on that in particular. We've historically resisted this kind of special case optimization, and yet the optimization is likely to be very effective in many representative cases. Plus, some aspects of the cost model are a bit fuzzy, in a way that things in the executor ordinarily are not, and so I can understand how this would present any reviewer with difficulty. By the way, the original description of this approach to accelerating sorts I saw was here, in this 2001 paper: http://lgis.informatik.uni-kl.de/archiv/wwwdvs.informatik.uni-kl.de/courses/DBSREAL/SS2001/Vorlesungsunterlagen/Implementing_Sorting.pdf (Under "2.4 Cache-optimized techniques") -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
