<div dir="ltr"><div class="gmail_extra"><br /><div class="gmail_quote">On 3 September 2014 01:08, Jan Wieck <span
dir="ltr"><<ahref="mailto:jan@wi3ck.info" target="_blank">jan@wi3ck.info</a>></span> wrote:<br /><blockquote
class="gmail_quote"style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 09/02/2014
06:56PM, Andrew Dunstan wrote:<br /><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">People are free to do what they want, but to my mind that would be a<br /> massive waste of
resources,and probably imposing a substantial extra<br /> maintenance burden on the core committers.<br
/></blockquote><br/></div> I hear you and agree to some degree.<br /><br /> But at the same time I remember that one of
thestrengths of Postgres used to be to be able to incorporate "new" ideas.<br /><br /> This seems to be one of those
cases.<br/><br /> Instead of "fork" plpgsql2, what about designing a completely new PL/postgres from scratch? It will
onlytake 3-10 years, but I bet it will be worth it after all. And I mean that. No sarcasm.<div class="im HOEnZb"><br
/></div></blockquote></div><br/></div><div class="gmail_extra">And how it would be better then already existing
plperl/plpython?<br/><br /></div><div class="gmail_extra">- Szymon<br /></div></div>
