| From: | James William Pye <lists(at)jwp(dot)name> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Nathan Boley <npboley(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, jd(at)commandprompt(dot)com, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plpython3 |
| Date: | 2010-02-01 21:38:48 |
| Message-ID: | 149DB906-BE28-4627-8B60-1129B64EF4B4@jwp.name |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 1, 2010, at 2:13 PM, Bruce Momjian wrote:
> I would love to know why PL/Python can't be incrementally improved like
> the rest of our code.
AFAICT, there are two primary, perhaps identifying, parts to a PL extension: code management (compilation, execution, etc) and type I/O (conversion in most PLs). (well, aside from the language itself =)
My proposed extension chooses a different design for both of those parts.
It didn't make sense to try and incrementally change PL/Python because I would have been rewriting the whole thing anyways. Not to mention breaking user code in the process for the mentioned parts--thus the Python 3 target.
Hope this clears things up.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2010-02-01 21:39:12 | Re: plpython3 |
| Previous Message | Jesper Krogh | 2010-02-01 21:33:49 | Make TOAST_TUPLES_PER_PAGE configurable per table. |