Re: [HACKERS] Re: [ADMIN] maximum attribute record.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: Jan Kim <kim(at)mpiz-koeln(dot)mpg(dot)de>, Vikrant Rathore <vikrant(at)chemquick(dot)com>, Postgres GOD <postgres(at)pili(dot)adn(dot)edu(dot)ph>, pgsql-admin(at)postgreSQL(dot)org, PostgreSQL-development <hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Re: [ADMIN] maximum attribute record.
Date: 1999-05-09 17:04:35
Message-ID: 2336.926269475@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> Has this been fixed in 6.5 beta?
>> On Tue, Feb 02, 1999 at 07:33:48PM +0800, Vikrant Rathore wrote:
>>
>>>> If your query is bigger than 8192 bytes then libpq simply truncates it
>>>> without giving any warning
>>
>> I've read that in the docs, too (while back, didn't try it out).

That hasn't been true since at least 6.3.2:

/* check to see if the query string is too long */
if (strlen(query) > MAX_MESSAGE_LEN - 2)
{
sprintf(conn->errorMessage, "PQsendQuery() -- query is too long. "
"Maximum length is %d\n", MAX_MESSAGE_LEN - 2);
return 0;
}

Possibly the documentation needs updated, but all I can find is:

: Caveats
:
: The query buffer is 8192 bytes long, and queries over that length will
: be rejected.

Is there another place that says the wrong thing?

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-05-09 17:21:59 Re: [HACKERS] ODMG interface
Previous Message Tom Lane 1999-05-09 16:58:13 Re: [HACKERS] Re: INSERT/UPDATE waiting (another example)