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

From Bruce Momjian
Subject Re: Replacing plpgsql's lexer
Date
Msg-id 200904142349.n3ENnur25728@momjian.us
Whole thread Raw
In response to Re: Replacing plpgsql's lexer  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Replacing plpgsql's lexer  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Replacing plpgsql's lexer  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Tom Lane wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
> > On Tue, 2009-04-14 at 16:37 -0400, Tom Lane wrote:
> >> Comments, objections, better ideas?
> 
> > Please, if you do this, make it optional.
> 
> I don't think making the plpgsql lexer pluggable is realistic.
> 
> > Potentially changing the behaviour of thousands of functions just to fix
> > a rare bug will not endear us to our users. The bug may be something
> > that people are relying on in some subtle way, ugly as that sounds.
> 
> That's why I don't want to change it in a minor release.  In a major
> release, however, it's fair game.

Well, this bug has existed long before 8.4 so we could just leave it for
8.5, and it is not like we have had tons of complaints;  the only
complaint I saw was one from March, 2008.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: proposal: add columns created and altered to pg_proc and pg_class
Next
From: Tom Lane
Date:
Subject: Re: Replacing plpgsql's lexer