Re: plpython3 - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: plpython3
Date
Msg-id 4B4D46B6.90808@agliodbs.com
Whole thread Raw
In response to Re: plpython3  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: plpython3  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: plpython3  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
> So it seems to me that the threshold question for this patch is - do
> we think it's a good idea to maintain two implementations of PL/python
> in core?

Not really, no.  This is why we need PGAN ;-)

If the new implementation is *better* that the existing PL/python, I
could see eventually replacing it.  It wouldn't be the first time that a
rewrite exceeded the original tool.

However, I'm not in a position to judge quality.

--Josh Berkus


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Streaming replication status
Next
From: Jaime Casanova
Date:
Subject: Re: lock_timeout GUC patch