Re: Select parser at runtime

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ian Lance Taylor <ian(at)airs(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Select parser at runtime
Date: 2001-08-11 20:35:14
Message-ID: 16548.997562114@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Ian Lance Taylor <ian(at)airs(dot)com> writes:
> This patch doesn't actually replace the entire backend/parser
> subdirectory. It mainly only replaces scan.l and gram.y. This is
> because the code in postgres.c still passes the result of the replaced
> parser to pg_analyze_and_rewrite().

Oh, of course, how silly of me. I was thinking that that call did the
analyze step too, but you're correct that it does not. Okay, replacing
lexer+syntaxer is a more reasonable chunk-size. (AFAIK there's no good
way to replace just part of a yacc/bison grammar on the fly, so you
couldn't go to a finer grain anyway, could you?)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Clift 2001-08-11 20:48:53 Re: CREATE LANGUAGE
Previous Message Ian Lance Taylor 2001-08-11 17:01:58 Re: Select parser at runtime

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2001-08-11 20:59:49 Re: [PATCHES] Select parser at runtime
Previous Message Timothy H. Keitt 2001-08-11 19:55:37 Re: Re: Fuzzy matching?