pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Roberto Mello <rmello@cc.usu.edu>
Cc: Jeff Barrett <jbarrett@familynetwork.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Memory exhausted in AllocSetAlloc(269039)
Date: Wed, 05 Dec 2001 11:48:32 -0500
Message-ID: <12163.1007570912@sss.pgh.pa.us> (raw)
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>

Roberto Mello <rmello@cc.usu.edu> 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



view thread (4+ messages)

Message-ID: <12163.1007570912@sss.pgh.pa.us>
Permalink:  ../12163.1007570912@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/12163.1007570912@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, rmello@cc.usu.edu, jbarrett@familynetwork.com
  Subject: Re: Memory exhausted in AllocSetAlloc(269039)
  In-Reply-To: <12163.1007570912@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox