From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
---|---|
To: | James William Pye <lists(at)jwp(dot)name> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, jd(at)commandprompt(dot)com, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: plpython3 |
Date: | 2010-01-15 02:08:08 |
Message-ID: | 4B4FCE08.9060801@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
James William Pye wrote:
> The documentation is back up, so please be sure to look at the numerous examples provided therein. In addition to that, I'll try to get some contrasting examples posted as a follow-up to an earlier message. "In plpython you do X whereas in plpython3 you do Y."
>
I had read the documentation before so it wasn't that bad that I
couldn't see it. Basically, the issue I had is that it's not really
clear which features are unique to this implementation that make it
compelling. So more targeted examples like you're considering now would
help.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-01-15 02:22:35 | PG_MODULE_MAGIC checks and pg_migrator |
Previous Message | Robert Haas | 2010-01-15 01:49:26 | Re: KNNGiST for knn-search (WIP) |