| From: | Joel Jacobson <joel(at)trustly(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL 2 |
| Date: | 2014-09-01 11:30:29 |
| Message-ID: | CAASwCXd4obEFkqS2sfXuzXT7eaBg1gM8GmKxUJFGCNunoa5hDA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 1, 2014 at 12:55 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> The likelihood of us now knowing all the things that we want to break
> rigth now seems about zero. There *will* be further ones. If we go with
> the approach of creating new language versions for all of them we'll end
> up with a completely unmaintainable mess. For PG devs, application dev
> and DBAs.
PL/pgSQL was added in 1998 (16 years ago).
Compared this with again Python:
1994 Python 1.0
2000 Python 2.0 (6 years later)
2008 Python 3.0 (8 years later)
Of course we don't know all the things we want to break in the *future*,
but there is a good chance all users of PL/pgSQL know what they want
to change *today*,
thanks to the 16 years of active development in the language.
In 16 years from now, maybe there is a need for PL/pgSQL 3, or maybe
not, who knows.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2014-09-01 11:40:01 | Re: PL/pgSQL 2 |
| Previous Message | Pavel Stehule | 2014-09-01 11:30:21 | Re: PL/pgSQL 2 |