| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Roberto Mello <rmello(at)cc(dot)usu(dot)edu> |
| Cc: | Jeff Barrett <jbarrett(at)familynetwork(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Memory exhausted in AllocSetAlloc(269039) |
| Date: | 2001-12-05 16:48:32 |
| Message-ID: | 12163.1007570912@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Roberto Mello <rmello(at)cc(dot)usu(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2001-12-05 18:14:47 | Re: Any patch for delete and insert same row in a function ( |
| Previous Message | Roberto Mello | 2001-12-05 15:55:15 | Re: Memory exhausted in AllocSetAlloc(269039) |