Re: Replacing plpgsql's lexer

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Replacing plpgsql's lexer
Date: 2009-04-15 12:27:38
Message-ID: 49E5D2BA.7030009@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
> How do you know which is the offending function? If we force a full
> application retest we put in place a significant barrier to upgrade.
> That isn't useful for us as developers, nor is it useful for users.
>
>

We support back branches for a long time for a reason. Nobody in their
right mind should upgrade to a new version without without first
extensively testing (and if necessary adjusting) their application on
it. This is true regardless of this issue and will be true for every
release.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Grzegorz Jaśkiewicz 2009-04-15 12:31:33 Re: Performance of full outer join in 8.3
Previous Message Robert Haas 2009-04-15 12:27:34 Re: Replacing plpgsql's lexer