Re: [HACKERS] Status report: long-query-string changes - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: [HACKERS] Status report: long-query-string changes
Date
Msg-id 37DC7074.1C1ACAA1@alumni.caltech.edu
Whole thread Raw
In response to Status report: long-query-string changes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Thomas Lockhart should speak up - he seems the only person who
> has objections yet. If the proposed thing is to be declined, something
> has to be applied instead in respect to lexer reject feature and
> accompanying size limits, as well as grammar inconsistency.

Hmm. I'd suggest that we go with the "greedy lexer" solution, which
continues to gobble characters which *could* be an operator until
other characters or whitespace are encountered.

I don't recall any compelling cases for which this would be an
inadequate solution, and we have plenty of time until v6.6 is released
to discover problems and work out alternatives.

Sorry for slowing things up; but fwiw I *did* think about it some more
;)
                   - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Fixing Simms' vacuum problems]
Next
From: Thomas Lockhart
Date:
Subject: Re: [HACKERS] Status report: long-query-string changes