No, it appears that the flex module doesn't handle any tokens with a length
above this value.  I didn't realise that it happened at about 4k in normal
operation though; I had intentionally set my YY_BUF_SIZE to 4096 to try some
testing.  I thought that this was causing the problem.  

Does anybody know (scan.l, parse.l) reasonably intimately?  Any info
regarding this would be appreciated?  Somebody mentioned this to me in mail
regarding the query string length 

>> -----Original Message-----
>> From: Natalya S. Makushina [mailto:mak@rtsoft.msk.ru]
>> Sent: Tuesday, August 17, 1999 3:15 PM
>> To: 'pgsql-hackers@postgreSQL.org'
>> Subject: [HACKERS] Problem with query length
>> 
>> 
>> -------------------------------------------------------------
----------------------------------------------------------------
>> I have posted this mail to psql-general.  But i didn't get 
>> any answer yet.
>> -------------------------------------------------------------
----------------------------------------------------------------
>> 
>> When i had tried to insert into text field text (length 
>> about 4000 chars), the backend have crashed with status 139. 
>> This error is happened when the query length ( SQL query) is 
>> more than 4095 chars. I am using PostgreSQL 6.4.2 on Linux.
>> 
>> My questions are:
>> 1. Is there problem with text field or with length of SQL query?
>> 2. Would postgresql have any limits for SQL query length?
>> I checked the archives but only found references to the 8K 
>> limit. Any help would be greatly appreciated.
>> Thanks for help
>> 				Natalya Makushina 
>> 				mak@rtsoft.msk.ru
>> 
>> 

Tue, 17 Aug 1999 15:49:26 +0200
"Ansley, Michael" <Michael.Ansley@intec.co.za>
RE: [HACKERS] Problem with query length