Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 3EA522E0083 for ; Mon, 28 Jan 2008 04:18:15 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 64526-03 for ; Mon, 28 Jan 2008 04:18:08 -0400 (AST) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by postgresql.org (Postfix) with ESMTP id 87E6A2E0167 for ; Mon, 28 Jan 2008 04:18:11 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id m38so3092972waf.5 for ; Mon, 28 Jan 2008 00:18:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=P4xhQhz21ysHCV6dY9YsTBXUzhuR3/mFOydA1dDgz9A=; b=fvxeT0+7hKYCQhvkwhdHHIM9gnlFp+HPnOCoul3yRdXvU2NOz590uCU4B3IWEn57g3zQdE27KluL9iPQJyBrn/61jYUNtSHeYdajsGin3ThJ2RTsGrvtvLKD/3icMWC3sWERD8OfjsLlopp6yHWN6oCKr1gA+ke3+ce5JgogNLM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VvBh+5j4HYgjM15wQUPLo7vJXtYGStvaouzwNkJarpocdp84sHOF3jWCFAD4667eIuy5xBu7C0hl6yRLN0bb3L4lBEks3bztHU1F1vDWixWc1m+hB+jVJs3LWlhjeQK4iQQX+G7ox4bJl7ay45LX1t0VHbG/JTJuRGR92lrlMAk= Received: by 10.115.76.1 with SMTP id d1mr1554233wal.108.1201508288812; Mon, 28 Jan 2008 00:18:08 -0800 (PST) Received: by 10.114.155.9 with HTTP; Mon, 28 Jan 2008 00:18:08 -0800 (PST) Message-ID: <1d4e0c10801280018x17103cc8o7ead9fdc75d69470@mail.gmail.com> Date: Mon, 28 Jan 2008 09:18:08 +0100 From: "Guillaume Smet" To: "Tom Lane" Subject: Re: 8.3rc1 Out of memory when performing update Cc: "Stephen Denne" , pgsql-performance@postgresql.org In-Reply-To: <22975.1201236625@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <21675.1201228274@sss.pgh.pa.us> <22975.1201236625@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/258 X-Sequence-Number: 28497 On Jan 25, 2008 5:50 AM, Tom Lane wrote: > Hmm. I think what that really means is you haven't got to the part of > the query where the leak is :-(. In my attempt to reproduce this > I found that 8.3 has introduced a memory leak into the RI trigger > support, such that even if an UPDATE doesn't change the FK columns > it's still likely to leak a few dozen bytes per updated row. > > Please see if the attached patch makes it better for you. Just FYI, somebody on #postgresql had the exact same problem of memleaks during update yesterday and your patch fixed it for him too. -- Guillaume