Re: pl/python custom datatype parsers - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pl/python custom datatype parsers
Date
Msg-id AANLkTikOcPYTp9tH6RLzRkew2p4ijS8VwZVCjWmAuON0@mail.gmail.com
Whole thread Raw
In response to Re: pl/python custom datatype parsers  (Jan Urbański <wulczer@wulczer.org>)
List pgsql-hackers
On Fri, Feb 11, 2011 at 10:49 AM, Jan Urbański <wulczer@wulczer.org> wrote:
> On 11/02/11 16:43, Robert Haas wrote:
>> On Sun, Feb 6, 2011 at 1:01 PM, Jan Urbański <wulczer@wulczer.org> wrote:
>>>> That's it for now. It is an exciting feature and plpython will be the
>>>> first language to think of when you're building "object database" if
>>>> this feature is in. The design here will affect following pl/perl and
>>>> other so it is important enough to discuss.
>>>
>>> Yes, I ended up writing this patch as a PoC of how you can integrate
>>> procedural languages with arbitrary addon modules, so it would be good
>>> to have a discussion about the general mechanisms. I'm aware that this
>>> discussion, and subsequently this patch, might be punted to 9.2
>>> (although that would be a shame).
>>
>> It's not clear to me from this discussion whether this patch (a) now
>> works and has consensus, and should be committed, (b) still needs more
>> discussion, but hopes to make it into 9.1, or (c) is now 9.2 material.
>
> I believe it's (b). But as we don't have time for that discussion that
> late in the release cycle, I think we need to consider it identical to (c).

OK, I'll mark it Returned with Feedback.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Alex Hunsaker
Date:
Subject: Re: pl/python invalidate functions with composite arguments
Next
From: Stephen Frost
Date:
Subject: Re: Add support for logging the current role