Re: Re: [PATCHES] Select parser at runtime - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [PATCHES] Select parser at runtime
Date
Msg-id 22026.997725516@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [PATCHES] Select parser at runtime  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> Things like VACUUM and ANALYZE, which you will have to keep unless you
> want to implement an Oracle storage manager as well. ;-)

Evidently Ian is just interested in a parser that could be used by
Oracle-compatible applications, which'd not be invoking such operations
anyway.  Maintenance scripts would have to use the regular PG parser.
That doesn't seem unreasonable.

Based on his further explanation, it seems that tracking grammar changes
wouldn't be an issue, but tracking parsetree changes definitely would
be.  I'm also still concerned about whether this can be done within the
parse step (no database access).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Re: [PATCHES] Select parser at runtime
Next
From: Doug McNaught
Date:
Subject: Re: Re: AW: Re: OID wraparound: summary and proposal