| From: | Szymon Guz <mabewlun(at)gmail(dot)com> |
|---|---|
| To: | Jan Wieck <jan(at)wi3ck(dot)info> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Álvaro Hernández Tortosa <aht(at)nosys(dot)es>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL 2 |
| Date: | 2014-09-03 06:15:15 |
| Message-ID: | CAFjNrYuqgn1BJRJNhhfPUw=pvSodDC5o+OuUP4myEopenRy+oA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3 September 2014 01:08, Jan Wieck <jan(at)wi3ck(dot)info> wrote:
> On 09/02/2014 06:56 PM, Andrew Dunstan wrote:
>
>> People are free to do what they want, but to my mind that would be a
>> massive waste of resources, and probably imposing a substantial extra
>> maintenance burden on the core committers.
>>
>
> I hear you and agree to some degree.
>
> But at the same time I remember that one of the strengths of Postgres used
> to be to be able to incorporate "new" ideas.
>
> This seems to be one of those cases.
>
> Instead of "fork" plpgsql2, what about designing a completely new
> PL/postgres from scratch? It will only take 3-10 years, but I bet it will
> be worth it after all. And I mean that. No sarcasm.
>
>
And how it would be better then already existing plperl/plpython?
- Szymon
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2014-09-03 07:14:14 | Re: PL/pgSQL 2 |
| Previous Message | Pavel Stehule | 2014-09-03 05:54:09 | Re: PL/pgSQL 2 |