Re: Python setof patch

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Gerrit van Dyk <gvandyk(at)agileworks(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Python setof patch
Date: 2005-07-05 17:51:55
Message-ID: 42CAC8BB.4000206@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Michael Fuhr wrote:

>On Tue, Jul 05, 2005 at 01:14:25PM -0400, Tom Lane wrote:
>
>
>>Aside from minor problems like being broken and undocumented, there is a
>>more serious question here: is this even the functionality we want?
>>
>>
>
>I'd rather see something akin to PL/pgSQL's RETURN NEXT or PL/Perl's
>return_next.
>
>
>

Agreed. My rudimentary testing shows that plperl's shiny new return_next
functionality not only avoids memory blowup but has a 40% speed
improvement over the old 'return the lot at once' API.

cheers

andrew

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2005-07-05 18:13:41 Re: [PATCHES] HEAD doesn't cope with libraries in non-default
Previous Message Jim C. Nasby 2005-07-05 17:43:55 Re: [PATCHES] HEAD doesn't cope with libraries in non-default