Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 749BA9FA195 for ; Tue, 16 Oct 2007 11:23:05 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 90604-01-9 for ; Tue, 16 Oct 2007 11:22:56 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by postgresql.org (Postfix) with ESMTP id 4D2EB9FA004 for ; Tue, 16 Oct 2007 11:22:56 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id j3so84817ugf for ; Tue, 16 Oct 2007 07:22:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=jPxqoJHQD41HCtN0nOOWpbVxRKxIMgPkDkbw3m1CyPc=; b=Lh69fKIAEEwTOr/MtaI6pSDgRGPswC1i1IOjW+3bUneV4n0vK9eeDaD5/1qQFLEuOC6omtz/pJkMgQ0ePJAz2cS+Qcyt7jR1ipbn6s4NgznRH4M6GwVkaj4JVig+P2diD6htbTL1F6Vmciagufyz7FTevhHP1V44XQvgUpfECUA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dkdCE57Bx/QZ6JHXbpGZWMEBkFGSc+k/OgZFmN/kbzgOzs0ukTLr0f/i05bWzDDV5VcNdBEywwDyYfnzMsqsu9N9uAqZGgIf56Cs2CWxqPKWuJ1nvoYxzB4FWlAEHSWrKKe1GiqfsbsChyNuMsGwVxoTnP8Cktw3cG4b6QQKnWQ= Received: by 10.66.218.15 with SMTP id q15mr9175442ugg.1192544574390; Tue, 16 Oct 2007 07:22:54 -0700 (PDT) Received: by 10.67.29.6 with HTTP; Tue, 16 Oct 2007 07:22:54 -0700 (PDT) Message-ID: Date: Tue, 16 Oct 2007 09:22:54 -0500 From: "Scott Marlowe" To: "Jason Lustig" Subject: Re: Autovacuum running out of memory Cc: "Richard Huxton" , pgsql-performance@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <374EB3D1-EE74-4B8C-9EEC-104ADD097568@brandeis.edu> <4714A458.5060408@archonet.com> <4714AD30.6000103@archonet.com> <57031F92-40D5-4832-8B76-FB73E510C735@brandeis.edu> <4714C426.3080207@archonet.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/178 X-Sequence-Number: 27200 On 10/16/07, Jason Lustig wrote: > I ran "ulimit -a" for the postgres user, and here's what I got: > > core file size (blocks, -c) 200000 > data seg size (kbytes, -d) 200000 > max nice (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 32635 > max locked memory (kbytes, -l) 32 > max memory size (kbytes, -m) 200000 > open files (-n) 100 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > max rt priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 100 > virtual memory (kbytes, -v) 200000 > file locks (-x) unlimited There ya go. it's limited to 200M memory. Generally speaking, limiting postgresql to something that small is not a good idea. Set it to ~ 1 Gig or so and see how it works.