Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 498D49FA46C for ; Tue, 16 Oct 2007 12:10:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 72747-05 for ; Tue, 16 Oct 2007 12:10:25 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2F84E9FA484 for ; Tue, 16 Oct 2007 12:10:24 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l9GFAHn4016501; Tue, 16 Oct 2007 11:10:17 -0400 (EDT) To: Richard Huxton cc: Jason Lustig , pgsql-performance@postgresql.org Subject: Re: Autovacuum running out of memory In-reply-to: <4714AD30.6000103@archonet.com> References: <374EB3D1-EE74-4B8C-9EEC-104ADD097568@brandeis.edu> <4714A458.5060408@archonet.com> <4714AD30.6000103@archonet.com> Comments: In-reply-to Richard Huxton message dated "Tue, 16 Oct 2007 13:23:12 +0100" Date: Tue, 16 Oct 2007 11:10:17 -0400 Message-ID: <16500.1192547417@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/183 X-Sequence-Number: 27205 Richard Huxton writes: > Hmm - odd that you're not getting any connection details. Not really; the autovacuum process doesn't have any connection, so those log_line_prefix fields will be left empty. The weird thing about this is why the large maintenance_work_mem works for a regular session and not for autovacuum. There really shouldn't be much difference in the maximum workable setting for the two cases, AFAICS. Your later suggestion to check out the postgres user's ulimit -a settings seems like the appropriate next step, but I'm not seeing how ulimit would affect only some of the postmaster's children. regards, tom lane