Skip site navigation (1) Skip section navigation (2)

Re: Enable pl/python to return records based on multipleOUT params

From: Hannu Krosing <hannu(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Enable pl/python to return records based on multipleOUT params
Date: 2008-11-04 06:52:12
Message-ID: 1225781532.7597.19.camel@huvostro (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, 2008-11-03 at 19:07 -0500, Tom Lane wrote:
> Hannu Krosing <hannu(at)2ndQuadrant(dot)com> writes:
> > On Sat, 2008-11-01 at 06:13 +0200, Hannu Krosing wrote:
> >> This version is quite rough, though passes tests here.
> >> 
> >> I will clean it up more during commitfest.
> 
> > probably still more things to do
> 
> The status of this patch isn't clear --- are you still working on it?
> There certainly appear to be a lot of debug leftovers that need to
> be removed, error messages to clean up, etc.

It passes all existing regression tests and works fine for "correct"
use, but even the code currently in CVS crashes the backend for this

py=# create or replace function add_any(in i1 anyelement, in i2
anyelement, out t text) language plpythonu as $$
return i1 + i2
$$;
CREATE FUNCTION
py=# select * from add_any(1,2);
server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!> 

Though it is a somewhat separate problem from current patch I'd like to
do something about it before having it all committed, as the fix must
touch the very same places than this patch.

I think it takes two-tree days to figure out proper way to fix it. 

I'd like it to just accept ANY* and do the right thing but I may end up
just rejecting ANY* on both IN and OUT args.

------------------------------------------
Hannu Krosing   http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability 
   Services, Consulting and Training


In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2008-11-04 07:23:31
Subject: Re: Bitmap Indexes patch (was Re: Bitmap Indexes:request for feedback)
Previous:From: Mark KirkwoodDate: 2008-11-04 05:33:54
Subject: Hot standby v5 patch - Databases created post backup remain inaccessible + replica SIGSEGV when coming out of standby

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group