Re: PL/pgSQL 2 - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: PL/pgSQL 2
Date
Msg-id 540443D0.4060609@joh.to
Whole thread Raw
In response to Re: PL/pgSQL 2  (Hannu Krosing <hannu@2ndQuadrant.com>)
Responses Re: PL/pgSQL 2
Re: PL/pgSQL 2
Re: PL/pgSQL 2
List 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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Make LWLockAcquireCommon() inline?
Next
From: Joel Jacobson
Date:
Subject: Re: PL/pgSQL 2