Received: from siren.shore.net (siren.shore.net [207.244.124.5])
	by hub.org (8.9.2/8.9.1) with ESMTP id OAA18947
	for <pgsql-interfaces@postgresql.org>;
	Fri, 19 Feb 1999 14:47:18 -0500 (EST) (envelope-from ari@shore.net)
Received: from pm4-042.port.shore.net ([192.168.1.2]) [207.244.108.42]
	by siren.shore.net with esmtp (Exim)
	for pgsql-interfaces@postgreSQL.org
	id 10DvtL-0001yR-00; Fri, 19 Feb 1999 14:47:16 -0500
X-Sender: ari@shell1.shore.net
Message-Id: <v04003a03b2f36d9b3da5@[192.168.1.2]>
In-Reply-To: <Pine.LNX.4.04.9902181823560.8265-100000@maidast.retep.org.uk>
References: <v04003a0ab2f13dafd794@[192.168.1.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 19 Feb 1999 14:47:40 -0500
To: pgsql-interfaces@postgresql.org
From: Ari Halberstadt <ari@shore.net>
Subject: Re: [INTERFACES] JDBC: detecting lost backend; 8192 byte limit in
	queries

>On Wed, 17 Feb 1999, Ari Halberstadt wrote:
>> - how do I store more than 8192 bytes?
>...
>Another method, would be to split the messages into multiple rows, and add
>a field to indicate the sequence.

This is what I ended up doing (resurrected some old code I'd chucked).
Thanks for the help.

-- Ari Halberstadt mailto:ari@shore.net <http://www.magiccookie.com/>
PGP public key available at <http://www.magiccookie.com/pgpkey.txt>