| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Joel Jacobson <joel(at)trustly(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL 2 |
| Date: | 2014-09-01 10:00:48 |
| Message-ID: | 540443D0.4060609@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/1/14 11:53 AM, Hannu Krosing wrote:
> On 09/01/2014 11:24 AM, Andres Freund wrote:
>> Look at the *disaster* the few minor changes in python3 were. It's now,
>> years after, only starting to get used again.
>>
>> You're going to have to find a more gradual way of doing this.
> Probably a better way (and there has been some talk of it) is
> having some kind of PRAGMA functionality, or pl/pgsql specific
> LOCAL SET to affect "just this function" and not spill to nested
> functions as is the case for SETs now.
I can't imagine how that would work for anyone who has thousands of
functions.
I've tried my best over the past ~year or so, but any attempts at
breaking backwards compatibility have been rejected. I really don't see
any gradual way of doing this. We either break things, live with what
we have right now, or create a new language.
.marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2014-09-01 10:11:35 | Re: PL/pgSQL 2 |
| Previous Message | Andres Freund | 2014-09-01 09:58:24 | Re: Make LWLockAcquireCommon() inline? |