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: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Enable pl/python to return records based on multipleOUT params
Date: 2008-11-27 08:26:32
Message-ID: 1227774392.8363.4.camel@huvostro (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, 2008-11-26 at 23:17 -0500, Robert Haas wrote:
> > 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.
> 
> The text above makes it sound like you're still working on this, but
> that was more than three weeks ago.  What is the status of this now?

It is ready to be applied without support for ANY*, just with the patch
for uninitialized pointer vector (uses pymalloc0 instead of pymalloc )
tom mentioned.

I am working on getting any supported as well though I was tied up with
other things wor last 1.5 weeks



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


In response to

pgsql-hackers by date

Next:From: Nikhil SontakkeDate: 2008-11-27 09:06:16
Subject: Re: Fwd: [PATCHES] Auto Partitioning Patch - WIP version 1
Previous:From: maosen.zhangDate: 2008-11-27 08:00:13
Subject: test

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