Re: Replacing plpgsql's lexer - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Replacing plpgsql's lexer
Date
Msg-id 49E5D2BA.7030009@dunslane.net
Whole thread Raw
In response to Re: Replacing plpgsql's lexer  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Replacing plpgsql's lexer  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Replacing plpgsql's lexer
Next
From: Robert Haas
Date:
Subject: Re: Replacing plpgsql's lexer