Tom Lane wrote: > Another pretty serious issue is that the current plpgsql lexer treats > various sorts of qualified names as single tokens. I had thought this > could be worked around in the interface layer by doing more lookahead. > You can do that, and it mostly works, but it's mighty tedious. The big > problem is that "yytext" gets out of step --- it will point at the last > token the core lexer has processed, and there's no good way to back it up > after lookahead. I spent a fair amount of time trying to work around that > by eliminating uses of "yytext" in plpgsql, and mostly succeeded, but > there are still some left. (Some of the remaining regression failures are > error messages that point at the wrong token because they rely on yytext.)
Just wondering if there are additional regressions not detected due to pg_regress using the ignore-whitespace option to diff. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
