pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Barrett <jbarrett@familynetwork.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Memory exhausted in AllocSetAlloc(269039)
Date: Tue, 04 Dec 2001 17:43:17 -0500
Message-ID: <6517.1007505797@sss.pgh.pa.us> (raw)
In-Reply-To: <9ujft0$2o2b$1@news.tht.net>
References: <9ujft0$2o2b$1@news.tht.net>

"Jeff Barrett" <jbarrett@familynetwork.com> writes:
> I have a function that takes a comma seperated string from another table and
> parses it into another table. When I run it on a string with 130 ids it
> works fine, when I run it on a string with 50,000 ids (each about 6
> characters long) I get the Error: Memory exhausted in AllocSetAlloc(269039).

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.

If you don't care to run beta code, you could possibly work around the
problem in 7.1 by subdividing your function.  Look in the archives for
a prior discussion of this issue (last summer, I think).

			regards, tom lane



view thread (4+ messages)  latest in thread

Message-ID: <6517.1007505797@sss.pgh.pa.us>
Permalink:  ../6517.1007505797@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6517.1007505797@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, jbarrett@familynetwork.com
  Subject: Re: Memory exhausted in AllocSetAlloc(269039)
  In-Reply-To: <6517.1007505797@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