Re: Speeding up the Postgres lexer

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Speeding up the Postgres lexer
Date: 2005-05-23 20:08:24
Message-ID: 1116878904.3844.396.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2005-05-23 20:34:54 Re: Speeding up the Postgres lexer
Previous Message Joe Conway 2005-05-23 20:04:50 Re: ARRAY() returning NULL instead of ARRAY[] resp. {}