Re: Re: [PATCHES] Select parser at runtime
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Ian Lance Taylor <ian@airs.com>, Vince Vielhaber <vev@michvhf.com>, Justin Clift <justin@postgresql.org>, PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2001-08-13T17:58:36Z
Lists: 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