> On the basis of all of the foregoing, I don't think we can consider
> this patch further for this CommitFest and will update
> commitfest.postgresql.org accordingly.

FWIW, I am very excited about this patch and would be happy to review
it but have been very busy over the past month. If I can promise a
review by Thursday morning could we keep it active? Hopefully, at the
very least, I can provide some useful feedback and spawn some
community interest.

I am worried that there is a bit of a chicken and an egg problem with
this patch. I code nearly exclusively in python and C, but I have
often found pl/python to be very unwieldy.  For this reason I often
use pl/perl or pl/pgsql for problems that, outside of postgres, I
would always use python. From the documentation, this patch seems like
an enormous step in the right direction.

-Nathan

In response to

• Re: plpython3 at 2010-02-01 18:20:47 from Robert Haas

Responses

• Re: plpython3 at 2010-02-01 20:12:41 from Joshua D. Drake
• Re: plpython3 at 2010-02-01 20:13:43 from Robert Haas
• Re: plpython3 at 2010-02-01 20:35:39 from Peter Eisentraut

pgsql-hackers by date

Next:	From: Joshua D. Drake	Date: 2010-02-01 20:12:41
	Subject: Re: plpython3
Previous:	From: Simon Riggs	Date: 2010-02-01 19:40:02
	Subject: Re: Hot Standby: Relation-specific deferred conflict resolution