| From: | Jim Nasby <jim(dot)nasby(at)openscg(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Joe Conway <mail(at)joeconway(dot)com> |
| Subject: | Re: Faster methods for getting SPI results (460% improvement) |
| Date: | 2017-04-07 04:11:58 |
| Message-ID: | 1DD10C2A-BF36-4D01-A9AC-99BD95394EB0@openscg.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Apr 6, 2017, at 9:10 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
>>> Why? We could very well return a somewhat "smarter" object. Returning
>>> rows row-by-row if accessed via iterator, materializes when accessed via
>>> row offset.
>>
>> I completely agree with that. What I don't understand is the objection to
>> speeding up the old access method. Or are you thinking we'd just abandon the
>> old method?
>
> What I'm saying is that we can do that transparently, with the current
> API. And there's no need to materialize anything in plpython, we can
> transparently use the SPI materialized version.
Oh, just switching from a list to an iterator. Ok, I finally get it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-04-07 04:11:59 | Re: Faster methods for getting SPI results (460% improvement) |
| Previous Message | Andres Freund | 2017-04-07 04:10:03 | Re: Faster methods for getting SPI results (460% improvement) |