Received: from noao.edu (noao.edu [140.252.1.54]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f66GTwa52423; Fri, 6 Jul 2001 12:29:58 -0400 (EDT) (envelope-from swampler@noao.edu) Received: from reynaud.tuc.noao.edu ([140.252.38.6] verified) by noao.edu (CommuniGate Pro SMTP 3.4.7) with ESMTP id 1319607; Fri, 06 Jul 2001 09:29:57 -0700 Received: from noao.edu (localhost [127.0.0.1]) by reynaud.tuc.noao.edu (8.9.1/8.9.1/SAG-04Feb01) with ESMTP id JAA25120; Fri, 6 Jul 2001 09:29:57 -0700 (MST) Message-ID: <3B45E785.6CAB7273@noao.edu> Date: Fri, 06 Jul 2001 09:29:57 -0700 From: Steve Wampler Organization: National Solar Observatory X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: postgres-jdbc , postgres-general Subject: Too much data received? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200107/174 X-Sequence-Number: 12091 PG 7.1.2, jdbc7.1-1.2.jar, RH Linux 6.2 (with upgrade to kernel 2.4.5 [and library upgrades]): I've got a table with 5 columns, two of which are type 'text' and intended to hold XMLized java objects (constructed using the JSX package). However, the XML tends to be pretty large (and I'll need *much* larger later). When attempting to insert a row through jdbc, I get an exception which (I assume) results from the size of the XML: Too much data was received. at org.postgresql.PG_Stream.ReceiveString(PG_Stream.java:306) at org.postgresql.Connection.ExecSQL(Connection.java:532) at org.postgresql.jdbc2.Statement.execute(Statement.java:294) at org.postgresql.jdbc2.Statement.executeUpdate(Statement.java:78) at OCS.database.DbServer.execute(DbServer.java:271) I seem to remember discussion on a limit in the jdbc driver that might be causing this, but couldn't find it in the psql-jdbc mail archives. Am I likely correct in this being the problem? Is there a fix in the works? Alternatively (and the reason this is cross posted to pgsql-general): Is there a better way to store these large XML strings than as a text type? If so, how? Ultimately, they may be many thousands of bytes long. Thanks! -- Steve Wampler- SOLIS Project, National Solar Observatory swampler@noao.edu