Re: Speeding up the Postgres lexer - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Speeding up the Postgres lexer
Date
Msg-id 1116878904.3844.396.camel@localhost.localdomain
Whole thread Raw
In response to Speeding up the Postgres lexer  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Speeding up the Postgres lexer  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, 2005-05-23 at 12:31 -0400, Tom Lane wrote:
> doesn't seem to be any way to get flex to complain if someone later
> makes a change that breaks the no-backup-cases property again.

After some digging, there is a  -b option will generate a file called
lex.backup if any backup-states exist. The file is said to contain
information that would help you remove backup-states. 

It seems straightforward to test for the existence of that file in the
build process? Or perhaps add a special test state --enable-flextest to
perform the test during the build.

Best Regards, Simon Riggs



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Obtaining Firing Statement clause in (pl/perlu) Trigger Function
Next
From: Andrew Dunstan
Date:
Subject: Re: Speeding up the Postgres lexer