Glenn Holmer wrote:
> Not sure if this is a JDBC or general Postgres question, but we're
> losing a web app's connection to Postgres with these errors:
> invalid string enlargement request size 1358954494
> AbortTransaction and not in in-progress state
This is the backend trying to allocate a very large string for some
reason, perhaps because of a silly-sized protocol message being received
or sent. Are you working with large bytea data at all?
> invalid frontend message type 41
And this is the protocol stream getting out of sync, possibly because of
the above error.
> This is with Postgres 7.4.7 and driver pg74.213.jdbc3.jar.
Can you try with the latest (build 310) driver and see if the problem
If so, can you send a testcase that demonstrates the problem? Or at
least the query code that fails plus the complete exception you get.
In response to
pgsql-jdbc by date
|Next:||From: Javier Yáñez||Date: 2005-03-17 09:50:33|
|Subject: Re: Charset encoding patch to JDBC driver|
|Previous:||From: Glenn Holmer||Date: 2005-03-16 20:58:36|
|Subject: invalid string enlargement request|