FW: Query string length

From: "Ansley, Michael" <Michael(dot)Ansley(at)intec(dot)co(dot)za>
To: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: FW: Query string length
Date: 1999-08-12 11:40:07
Message-ID: 1BF7C7482189D211B03F00805F8527F70ED0D8@S-NATH-EXCH2
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I forgot, tokens are still limited to 16kB ;-)

>> Right, it works. Patches will arrive as soon as I figure out how to get
cvs
>> to diff the whole lot into one patch. I managed to get a 97kB query
through,
>> where the normal max was 64kB. I have to warn though, it munches
memory.
>> Disappearing at a rate of about 6MB a second, my paltry 64MB RAM with
>> 100MB swap looked alarmingly small. Of course, if you're on a decent
server,
>> this becomes less of an issue, but it doesn't go away. Still, it's
better than
>> being limited to 64kB.

>> The main issue seemed to be scan.l I had to change myinput() to cope
with
>> multiple calls, rather than assuming that flex would call it once only
for the
>> entire query. As a matter of interest, the code seems to think that lex
might
>> still be used. Is this the case, or can I remove the lex-specific code,
i.e.: we
>> assume flex to be used ALWAYS.

> MikeA
>
>

Browse pgsql-hackers by date

  From Date Subject
Next Message Collin F. Lynch 1999-08-12 14:38:15 "20L" not interpreted as text.
Previous Message Ansley, Michael 1999-08-12 11:29:14 Query string length