From owner-freebsd-questions@FreeBSD.ORG Tue May 23 20:37:35 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCD5B16AAF4 for ; Tue, 23 May 2006 20:37:35 +0000 (UTC) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC2C643D73 for ; Tue, 23 May 2006 20:37:28 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 0E33698C96 for ; Tue, 23 May 2006 15:37:28 -0500 (CDT) X-Virus-Scanned: amavisd-new at honeypot.net Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z8pOMO42XuES for ; Tue, 23 May 2006 15:37:27 -0500 (CDT) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id AAA4C95856 for ; Tue, 23 May 2006 15:37:27 -0500 (CDT) From: Kirk Strauser To: freebsd-questions@freebsd.org User-Agent: KMail/1.9.1 X-Face: T+/_{qmjgbosI0J/e83I~w[&VF'w)!((xEpj///^bA/6?jHHS?nq+T8_+`nh"WnEWCWG, \}]Y2$)) =?iso-8859-1?q?vLVz4ACChrEcb=7DCO=5EtYmMG=5C=0A=09ts=2Em=3F=5B7=5B6OwE*dA?= =?iso-8859-1?q?J*9f+mX=2E7R32qeN=5EDJ=5C?=(k@evW?IRQCy.^ MIME-Version: 1.0 Content-Disposition: inline X-Length: 1637 X-UID: 759 Date: Tue, 23 May 2006 15:37:25 -0500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200605231537.26304.kirk@strauser.com> Subject: PostgreSQL uses more memory on 6.1? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 20:37:47 -0000 I just upgraded from 6-STABLE as of 2006-02-18 to 6-STABLE as of 2006-05-21, and was surprised to find that PostgreSQL wouldn't start because it couldn't allocate enough shared memory. Thing is, I didn't make a single hardware change during the reboot and didn't upgrade any ports on the machine. My emergency fix was to edit postgresql.conf to change shared_buffers from 8192 to 2048. Unfortunately, that seems to be hurting performance - I'm getting annoying deadlocks at 4AM whenever multiple daemons start their overnight batch runs. Has anyone else seen this behavior when upgrading from 6.0 to 6.1? Any ideas for a fix? I apologize for not having a logfiles, but I was pretty much in a panic to get it back up and running ASAP and didn't think about it until it was too late. -- Kirk Strauser