Re: [HACKERS] Window Functions: buffering strategy

2008-10-20 Thread Hitoshi Harada
2008/10/21 Heikki Linnakangas <[EMAIL PROTECTED]>: > Hitoshi Harada wrote: >> >> The real problem is not how to cut off preceding rows, but how to read >> ahead after the current row. I intend to avoid reading ahead until end >> of the partition for only row_number() that doesn't need any following

Re: [HACKERS] Window Functions: buffering strategy

2008-10-20 Thread Heikki Linnakangas
Hitoshi Harada wrote: The real problem is not how to cut off preceding rows, but how to read ahead after the current row. I intend to avoid reading ahead until end of the partition for only row_number() that doesn't need any following rows. Sometimes we have to store whole the partition before re

Re: [HACKERS] Window Functions: buffering strategy

2008-10-20 Thread Hitoshi Harada
2008/10/20 Heikki Linnakangas <[EMAIL PROTECTED]>: > Hitoshi Harada wrote: >> >> Hi, >> >> 2008/10/20 Simon Riggs <[EMAIL PROTECTED]>: >>> >>> On Mon, 2008-10-20 at 10:32 +0900, Hitoshi Harada wrote: >>> So I propose three Window node buffering strategies, row/frame/partition buffering so

Re: [HACKERS] Window Functions: buffering strategy

2008-10-20 Thread Heikki Linnakangas
Hitoshi Harada wrote: Hi, 2008/10/20 Simon Riggs <[EMAIL PROTECTED]>: On Mon, 2008-10-20 at 10:32 +0900, Hitoshi Harada wrote: So I propose three Window node buffering strategies, row/frame/partition buffering so as to avoid unnecessary row buffering. Sounds good from here. Can I suggest you

Re: [HACKERS] Window Functions: buffering strategy

2008-10-20 Thread Hitoshi Harada
Hi, 2008/10/20 Simon Riggs <[EMAIL PROTECTED]>: > > On Mon, 2008-10-20 at 10:32 +0900, Hitoshi Harada wrote: > >> So I propose three Window node buffering strategies, >> row/frame/partition buffering so as to avoid unnecessary row >> buffering. > > Sounds good from here. Can I suggest you release

Re: [HACKERS] Window Functions: buffering strategy

2008-10-19 Thread Simon Riggs
On Mon, 2008-10-20 at 10:32 +0900, Hitoshi Harada wrote: > So I propose three Window node buffering strategies, > row/frame/partition buffering so as to avoid unnecessary row > buffering. Sounds good from here. Can I suggest you release the code in phases? It would be better if we got just one

[HACKERS] Window Functions: buffering strategy

2008-10-19 Thread Hitoshi Harada
> I can find how to do it with the new (window execution model) design, > (and the design is suitable to fix it above,) but at first before > going into trivial specs, I would like core hackers to review the > model is better than before or not. Thank you for your cooperation. So no objections app