On 4/27/06, Tom Lane <[EMAIL PROTECTED]> wrote:
> ... and is far more maintainable than an RD parser, and is not a
> performance bottleneck. I've never seen yyparse occupy as much as 2%
> of a backend profile ...
Not more maintainable by any stretch of the imagination. For example,
try and remove the AS alias for columns in our bison grammar without
having to remove keywords from unreserved_keywords :) In PCCTS (or a
hand-written RD parser), it's VERY easy because you can control the
lookahead as necessary.
Now, in terms of performance, it's hard to beat a LALR parser, but LL
parsers are comparable if done correctly; especially if written by
hand. Besides, parsing itself isn't what kills us, it's the lack of
caching unprepared statements. Yes, this is another topic in and of
itself, but I know there was discussion about it between you and Neil;
did anything ever come of it?
--
Jonah H. Harris, Database Internals Architect
EnterpriseDB Corporation
732.331.1324
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
