X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 37FE230F2CE for ; Wed, 18 Jun 2003 07:10:41 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 63994-07 for ; Wed, 18 Jun 2003 04:10:30 -0300 (ADT) Received: from mail.deltav.hu (oldmail.deltav.hu [213.163.0.192]) by svr1.postgresql.org (Postfix) with ESMTP id 3ABC430F2C7 for ; Wed, 18 Jun 2003 04:10:29 -0300 (ADT) Received: from fejleszt4 ([213.163.10.103]) by mail.deltav.hu (Netscape Messaging Server 3.6) with SMTP id AAA6DDA for ; Wed, 18 Jun 2003 09:10:27 +0200 Message-ID: <004a01c33568$d48235c0$0403a8c0@fejleszt4> From: "=?utf-8?B?U1rFsENTIEfDoWJvcg==?=" To: References: <1055752337.2182.49.camel@kaos> <6634.1055796302@sss.pgh.pa.us><1055753856.5467.57.camel@kaos> <6892.1055799269@sss.pgh.pa.us><1055832411.5467.100.camel@kaos> <14875.1055878682@sss.pgh.pa.us> <1055842927.2182.227.camel@kaos> Subject: Re: Postgres Connections Requiring Large Amounts of Memory Date: Wed, 18 Jun 2003 09:11:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Archive-Number: 200306/122 X-Sequence-Number: 2206 ----- Original Message ----- From: "Dawn Hollingsworth" Sent: Tuesday, June 17, 2003 11:42 AM > I'm not starting any of my own transactions and I'm not calling stored > procedures from withing stored procedures. The stored procedures do have > large parameters lists, up to 100. The tables are from 300 to 500 Geez! I don't think it'll help you find the memory leak (if any), but couldn't you normalize the tables to smaller ones? That may be a pain when updating (views and rules), but I think it'd worth in resources (time and memory, but maybe not disk space). I wonder what is the maximum number of updated cols and the minimum correlation between their semantics in a single transaction (i.e. one func call), since there are "only" 100 params for a proc. > columns. 90% of the columns are either INT4 or INT8. Some of these > tables are inherited. Could that be causing problems? Huh. It's still 30-50 columns (a size of a fairly large table for me) of other types :) G. ------------------------------- cut here -------------------------------