Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by hub.org (8.8.8/8.8.8) with ESMTP id VAA05034 for ; Fri, 18 Sep 1998 21:55:57 -0400 (EDT) (envelope-from matthew@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id SAA13762 for ; Fri, 18 Sep 1998 18:55:26 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id SAA17066 for ; Fri, 18 Sep 1998 18:55:24 -0700 (PDT) Received: from baynetworks.com (corp-no-148 [132.245.139.148]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id VAA24160; Fri, 18 Sep 1998 21:55:23 -0400 for Message-ID: <36030EF8.4CBE1A09@baynetworks.com> Date: Fri, 18 Sep 1998 21:55:04 -0400 From: Matthew Liste Organization: Bay Networks X-Mailer: Mozilla 4.5b1 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: postgres process grows. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I'm accessing a database using JDBC, I keep a socket open for a long time and for multiple queries. My Java code for a query typically looks like: Statement sta = con.createStatement(); sta.executeQuery( "DELETE FROM TABLE" ); For some reason, the postgres daemon that gets forked on the DB server (Solaris 2.6, postgresql 6.3.2) keeps growing for each query that I execute, until it eats up all memory. Is there something I'm doing wrong in my queries, or is there a patch for this? Thanks for any help, -Matthew (matthew@baynetworks.com)