RE: [HACKERS] MAX Query length - Mailing list pgsql-hackers

From Ansley, Michael
Subject RE: [HACKERS] MAX Query length
Date
Msg-id 1BF7C7482189D211B03F00805F8527F70ED034@S-NATH-EXCH2
Whole thread Raw
Responses Re: [HACKERS] MAX Query length
List pgsql-hackers
Thanks for all the answers, everybody.  Bruce, I had thought to start work
adjusting this so that the size wasn't limited at all.  I'm just busy
gathering as much info as I can about the subject area, and hopefully in a
couple of days, if not earlier, I'll be in a position to start working on
the code.
I seem to remember there being a hackers guide somewhere.  If I remember
right, it dealt with issues like where to check out the latest source from
cvs, rough standards, and other basic advice.  Can anybody point me to it?

Thanks

MikeA

>> -----Original Message-----
>> From: Bruce Momjian [mailto:maillist@candle.pha.pa.us]
>> Sent: Wednesday, July 14, 1999 5:02 PM
>> To: Ansley, Michael
>> Cc: 'pgsql-hackers@postgresql.org'
>> Subject: Re: [HACKERS] MAX Query length
>> 
>> 
>> [Charset iso-8859-1 unsupported, filtering to ASCII...]
>> > 
>> > Trawling through the code last night I noticed that:
>> > #define MAX_QUERY_SIZE (BLCKSZ * 2)
>> > 
>> > Is there any conceivable reason why the query length would 
>> be dependent on
>> > the block size?  Or do I just have old source code?
>> 
>> No great reason, but is seems like a good maximum.  This controls the
>> buffer size on the client and server.  Do you need it larger?
>> 
>> -- 
>>   Bruce Momjian                        |  http://www.op.net/~candle
>>   maillist@candle.pha.pa.us            |  (610) 853-3000
>>   +  If your life is a hard drive,     |  830 Blythe Avenue
>>   +  Christ can be your backup.        |  Drexel Hill, 
>> Pennsylvania 19026
>> 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] What does explain show ?
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: 6.5.1 release