Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 35269 invoked from network); 14 Apr 2005 17:05:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Apr 2005 17:05:46 -0000 Received: (qmail 14230 invoked by uid 500); 14 Apr 2005 17:05:45 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 14046 invoked by uid 500); 14 Apr 2005 17:05:44 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 14033 invoked by uid 99); 14 Apr 2005 17:05:44 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from manta.curalia.se (HELO manta.curalia.se) (213.115.149.212) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 14 Apr 2005 10:05:43 -0700 Received: from [192.168.1.5] (unknown [80.64.176.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by manta.curalia.se (Postfix) with ESMTP id AB30FABC031 for ; Thu, 14 Apr 2005 19:05:40 +0200 (CEST) Message-ID: <425EA30E.9010204@apache.org> Date: Thu, 14 Apr 2005 19:06:22 +0200 From: =?ISO-8859-1?Q?Martin_Kal=E9n?= Organization: ASF User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: OJB Developers List Subject: PostgreSQL default JDBC fetch size hint Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Greetings, on the user list Andreas Bohnert has pointed out some memory problems when using the PostgreSQL JDBC driver and a large ResultSet, since the PostgreSQL JDBC client will fetch _all_ returned rows over the wire even when the ResulSet is iterated one row at a time with eg OJB getIteratorByQuery. See this thread: http://www.mail-archive.com/ojb-user%40db.apache.org/msg13380.html I have done some testing and it seems that explicit setting of the fetch size (a JDBC hint most drivers will ignore) does not cause any trouble with the OJB tests. See PB and ODMG results here: http://people.apache.org/~mkalen/ojb/postgresql-fetchsize-tests.html However, making fetchSize=1 a global PostgreSQL default in OJB will probably cause slightly more network traffic and JDBC overhead so there might be objections to checking in the new afterStatementCreate shown on my ASF webpage above. Any thoughts/comments on this? Does anyone know if PG7 vs PG8 JDBC-client and/or servers will do things differently wrt server-side cursors? Regards, Martin --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org