Re: Re: [PATCHES] Select parser at runtime

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: Ian Lance Taylor <ian(at)airs(dot)com>, Vince Vielhaber <vev(at)michvhf(dot)com>, Justin Clift <justin(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [PATCHES] Select parser at runtime
Date: 2001-08-13 14:23:24
Message-ID: 16777.997712604@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> files per parser and call the right one from tcop. Now for
> some flex/bison combo's at least the prefix switches (to have
> something different than YY) don't work reliable. There will
> be some global YY-objects left, causing linkage problems.
> That's why PL/pgSQL's scanner/parser's C-code is run through
> sed(1).

The only reason plpgsql's parser is still run through sed is that
I haven't gotten around to changing it ;-). The main system has
depended on -P for awhile, and we've seen no reports of trouble.

(This is not unrelated to the fact that we now ship pre-yacced and
pre-lexed .c files, no doubt. Only people who pull from CVS ever
rebuild the files at all, and we tell them they must use up-to-date
flex and bison. This policy seems to work a lot better than the old
way of trying to work with whatever broken tools a particular platform
might have...)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message gabriel 2001-08-13 14:27:05 Perl,Postmaster and CPU question??
Previous Message mlw 2001-08-13 14:17:25 Re: AW: Re: OID wraparound: summary and proposal

Browse pgsql-patches by date

  From Date Subject
Next Message Garrett Wollman 2001-08-13 15:26:42 Re: Patch: use SCM_CREDS authentication over PF_LOCAL sockets
Previous Message Tom Lane 2001-08-13 14:14:14 Re: Patch: use SCM_CREDS authentication over PF_LOCAL sockets