Simon Riggs <si...@2ndquadrant.com> writes: > Sounds very similar to the solution that you just removed from the hash > join code for performance reasons. Flushing memory when we overflow > sounds like an artifact from the time when tuplestore split from > tuplesort. Can't we keep the appropriate rows in memory and scroll > through them?
We're not doing a fundamental redesign of the window function support right now. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers