Re: plpgsql versus long ELSIF chains - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: plpgsql versus long ELSIF chains
Date
Msg-id 4EA98BA2.5070209@enterprisedb.com
Whole thread Raw
In response to plpgsql versus long ELSIF chains  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 27.10.2011 19:18, Tom Lane wrote:
> So really what needs to be done here is to make ELSIF chains explicit in
> the parsetree representation, and handle them via looping not recursion
> at runtime.  This will also make it a lot easier to do the grammar via
> left-recursion.
>
> So I'm going to go off and do that, but I wonder whether anyone thinks
> this is sufficiently important to back-patch.

This doesn't look like a bug to me, just an unoptimal implementation. So 
-1 for backpatching.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: plpgsql versus long ELSIF chains
Next
From: Simon Riggs
Date:
Subject: Re: Hot Standby startup with overflowed snapshots