Re: Faster methods for getting SPI results (460% improvement)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim Nasby <jim(dot)nasby(at)openscg(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Peter Eisentraut <peter(dot)eisentraut(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:59
Message-ID: 31192.1491538319@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim Nasby <jim(dot)nasby(at)openscg(dot)com> writes:
> On 4/6/17 8:13 PM, Tom Lane wrote:
>> Given Peter's objections, I don't think this is getting into v10 anyway,
>> so we might as well take a bit more time and do it right.

> Well, Peter's objection is that we're not going far enough in plpython,
> but there's absolutely no way to do more without breaking plpy, which
> seems a non-starter. We should certainly be able to expand the existing
> API to provide even more benefit, but I see no reason to leave the
> performance gain this patch provides on the floor just because there's
> more to be had with a different API.

Personally I'm way more excited about what a SPI feature like this
could do for plpgsql than about what it can do for plpython. If the
latter is what floats your boat, that's fine; but I want a feature
that we can build on for other uses, not a hack that we know we need
to redesign next month.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-04-07 04:12:09 Re: src/interfaces/libpq shipping nmake-related Makefiles
Previous Message Jim Nasby 2017-04-07 04:11:58 Re: Faster methods for getting SPI results (460% improvement)