Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fB4Mi4m24470 for ; Tue, 4 Dec 2001 17:44: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 fB4MhHi06520; Tue, 4 Dec 2001 17:43:17 -0500 (EST) To: "Jeff Barrett" cc: pgsql-sql@postgresql.org Subject: Re: Memory exhausted in AllocSetAlloc(269039) In-reply-to: <9ujft0$2o2b$1@news.tht.net> References: <9ujft0$2o2b$1@news.tht.net> Comments: In-reply-to "Jeff Barrett" message dated "Tue, 04 Dec 2001 16:36:27 -0500" Date: Tue, 04 Dec 2001 17:43:17 -0500 Message-ID: <6517.1007505797@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200112/42 X-Sequence-Number: 5865 "Jeff Barrett" 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