Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fB5Gn3m85071 for ; Wed, 5 Dec 2001 11:49:04 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id fB5GmWi12166; Wed, 5 Dec 2001 11:48:32 -0500 (EST) To: Roberto Mello cc: Jeff Barrett , pgsql-sql@postgresql.org Subject: Re: Memory exhausted in AllocSetAlloc(269039) In-reply-to: <20011205085514.A26052@cc.usu.edu> References: <9ujft0$2o2b$1@news.tht.net> <6517.1007505797@sss.pgh.pa.us> <20011205085514.A26052@cc.usu.edu> Comments: In-reply-to Roberto Mello message dated "Wed, 05 Dec 2001 08:55:15 -0700" Date: Wed, 05 Dec 2001 11:48:32 -0500 Message-ID: <12163.1007570912@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200112/49 X-Sequence-Number: 5872 Roberto Mello writes: > On Tue, Dec 04, 2001 at 05:43:17PM -0500, Tom Lane wrote: >> Seems to run fine in 7.2beta. Prior versions of plpgsql tended to leak >> memory within a function call, but that's been worked on in 7.2. > Would you please ellaborate on this leak? We are using PL/pgSQL heavily > on OpenACS and these details would help to make a decision to support 7.1 > or push for 7.2. I don't recall all the details, but some plpgsql constructs would use memory that wouldn't be reclaimed until function exit. So if you had a long-running loop inside a function, you could see memory problems. I'm not convinced that 7.2 is *entirely* free of such problems, but it's a lot better than 7.1 was. regards, tom lane