Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id D7A249FB259 for ; Tue, 16 Oct 2007 09:23:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 80788-08 for ; Tue, 16 Oct 2007 09:22:59 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from pih-relay08.plus.net (pih-relay08.plus.net [212.159.14.134]) by postgresql.org (Postfix) with ESMTP id 7D6849FB256 for ; Tue, 16 Oct 2007 09:23:15 -0300 (ADT) Received: from [84.51.143.99] (helo=server3.office.archonet.com) by pih-relay08.plus.net with esmtp (Exim) id 1IhlS4-0001vc-Jx; Tue, 16 Oct 2007 13:23:12 +0100 Received: from [192.168.1.36] (dell36.office.archonet.com [192.168.1.36]) by server3.office.archonet.com (Postfix) with ESMTP id 3819127404F; Tue, 16 Oct 2007 13:23:12 +0100 (BST) Message-ID: <4714AD30.6000103@archonet.com> Date: Tue, 16 Oct 2007 13:23:12 +0100 From: Richard Huxton User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Jason Lustig CC: pgsql-performance@postgresql.org Subject: Re: Autovacuum running out of memory References: <374EB3D1-EE74-4B8C-9EEC-104ADD097568@brandeis.edu> <4714A458.5060408@archonet.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/172 X-Sequence-Number: 27194 Jason Lustig wrote: > There isn't any more error message than this... it simply repeats every > minute or so, which is really quite strange. And the user & db is really > blank in the log, I didn't trim it (if I did I would have replaced it > with dummy values). Hmm - odd that you're not getting any connection details. > I'm using pg 8.2.4 on Linux 2.6.15. Fair enough. >>> Oct 16 06:43:47 [2897]: [1-1] user=,db= ERROR: out of memory >>> Oct 16 06:43:47 [2897]: [1-2] user=,db= DETAIL: Failed on request >>> of size 524287998. Well, since this is about 500MB and your maintenance_work_mem is set to 500MB that's the obvious place to start. It might just be that you've not got enough free memory. What happens if you set maintenance_work_mem to say 50MB? -- Richard Huxton Archonet Ltd