Re: [HACKERS] merging some features from plpgsql2 project - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] merging some features from plpgsql2 project
Date
Msg-id CAFj8pRCZwdyyzHWR2M7a-XVnx0HNPr4Eov6oF53mTaO5ti-4DA@mail.gmail.com
Whole thread Raw
In response to [HACKERS] merging some features from plpgsql2 project  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers


2016-12-27 8:54 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:
Hi

I reread ideas described on page https://github.com/trustly/plpgsql2

Some points are well and can be benefit for PlpgSQL.

First I describe my initial position. I am strongly against introduction "new" language - plpgsql2 or new plpgsql, or any else. The trust of developers to us is important and introduction of any not compatible or different feature has to have really big reason. PostgreSQL is conservative environment, and PLpgSQL should not be a exception. More - I have not any information from my customers, colleagues about missing features in this language.  If there is some gaps, then it is in outer environment - IDE, deployment, testing,


I forgot - the big plpgsql issue are too weak expressions on left  part of assignment statements.
 


Pavel

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: [HACKERS] Reporting planning time with EXPLAIN
Next
From: Mithun Cy
Date:
Subject: Re: [HACKERS] Cache Hash Index meta page.