Re: WIP patch: convert SQL-language functions to return tuplestores

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP patch: convert SQL-language functions to return tuplestores
Date: 2008-10-28 13:28:38
Message-ID: 19221.1225200518@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On Sun, 2008-10-26 at 21:49 -0400, Tom Lane wrote:
>> So I'm concluding that we can easily afford to switch to
>> tuplestore-always operation, especially if we are willing to put any
>> effort into tuplestore optimization. (I note that the current
>> tuplestore code writes 24 bytes per row for this example, which is a
>> shade on the high side for only 4 bytes payload. It looks like it
>> would be pretty easy to knock 10 bytes off that for a 40% savings in
>> I/O volume.)

> That seems like an important, possibly more important, change.

Yeah, seeing that both WITH and window functions will be stressing
tuplestore performance, anything we can save there is probably worth the
trouble.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kenneth Marshall 2008-10-28 13:32:52 Re: WIP patch: convert SQL-language functions to return tuplestores
Previous Message Tom Lane 2008-10-28 13:26:48 Re: WIP patch: convert SQL-language functions to return tuplestores