Re: plpgsql versus long ELSIF chains

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: plpgsql versus long ELSIF chains
Date: 2011-10-27 16:37:41
Message-ID: 979737CF-B65D-4544-BCBB-73C9A931BC85@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Oct 27, 2011, at 9:18 AM, Tom Lane wrote:

> So I'm going to go off and do that, but I wonder whether anyone thinks
> this is sufficiently important to back-patch. I'm inclined to think
> that back-patching isn't a good idea, because changing the
> representation of PLpgSQL_stmt_if will break (at least) EDB's plpgsql
> debugger; ISTM the number of complaints isn't enough to warrant doing
> that in released branches.

+1 to not back-patching. Seems like it doesn't come up all that often, right

Best,

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2011-10-27 16:49:38 Re: plpgsql versus long ELSIF chains
Previous Message Chris Redekop 2011-10-27 16:26:24 Re: Hot Standby startup with overflowed snapshots