Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WTXCg-0001qd-5J for pgsql-admin@arkaria.postgresql.org; Fri, 28 Mar 2014 13:52:14 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WTXCf-00077p-Kb for pgsql-admin@arkaria.postgresql.org; Fri, 28 Mar 2014 13:52:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WTXCd-00077c-DG; Fri, 28 Mar 2014 13:52:11 +0000 Received: from new2-smtp.messagingengine.com ([66.111.4.224]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WTXCZ-0007mt-Az; Fri, 28 Mar 2014 13:52:10 +0000 Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C19569E7; Fri, 28 Mar 2014 09:52:04 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Fri, 28 Mar 2014 09:52:04 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=q5gurOC0UEO8EE+7SylKflfK3b0=; b=FPSnBGaL4RQTyYSJV3zGV/dvZYD7 ItSFgfJEa3wBnpxGQObdYTlZF5tnTLN4GUggPFa+MmS0OHJbxJTXpPmGpnUv6kTK eWyHDBqGXI3zPbLbTBRPwJ001YIdHO5B2413Oq6GsQ7rsqvr4X1JpTt3YLXY1P6g v0fYao70Syb/gYw= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=q5gurOC0UEO8EE+7SylKfl fK3b0=; b=a7xKszouwkYIQqP5iggigMBFBtq4r3vH6zanSvxaL6FHbUgePqYTwn fK2ytC+wCgfyhmhmfP1AeA2GPNgmzCH3isZ+9YSaRheVwZECG3S+fWlB4JbZNjEu Mbqn4nHPT6N1l9Ts8Z7qM4k1JG1BnTEwBrUWlp5bRyhWGapf2kJE8= X-Sasl-enc: bNMWq+3YW/lXwRNqoMHRP0AdgIv9pAPV+W+KySPwMXIv 1396014724 Received: from panda.site (unknown [97.113.11.16]) by mail.messagingengine.com (Postfix) with ESMTPA id E59256800D7; Fri, 28 Mar 2014 09:52:03 -0400 (EDT) Message-ID: <53357E83.2040101@aklaver.com> Date: Fri, 28 Mar 2014 06:52:03 -0700 From: Adrian Klaver User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Willy-Bas Loos , pgsql-admin , "pgsql-general@postgresql.org" Subject: Re: [GENERAL] openvz and shared memory trouble References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -0.9 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On 03/28/2014 01:51 AM, Willy-Bas Loos wrote: > Hi, > > I have a problem with postgres in combination with openvz. > My hot standby crashes on me when i give it a normal value for > shared_buffers (4GB, which 25% of the memory in the container). > When i tune down the shared_buffers, it works again. But of course this > is far from desireable. What is the error that shows up in the logs when the 'machine' crashes? 25% is a suggested value, not an absolute value. Desirable would seem to be a value that works for your situation and maintains performance. Is there any indication that running with a lower value adversely affects performance? > > Now, i've seen a couple more messages around the net about openVZ and > postgres that weren't very encouraging: > > http://www.postgresql.org/message-id/CAHyXU0xa5EgvjeH=4vp-eZDJdS5kMQuiDivvTRLjY-uZ62Y44w@mail.gmail.com > http://www.postgresql.org/message-id/23206.1254683408@sss.pgh.pa.us > http://postgresql.1045698.n5.nabble.com/BUG-9721-Fatal-error-on-startup-no-free-slots-in-PMChildFlags-array-td5797390.html > > But i am in a position where we already have a pretty strong binding > with openVZ. > I also have a colleague that has been using openVZ and postgres on > production for quite a while now, without any problems. And already 1 of > our servers is running a production database in openVZ that is well > used, without any trouble of this kind. > > Now, what i would like to know is: > > * is there clarity about what the issues are at all > * is it just 1 problem (in openVZ) that make openVZ and postgres so > poorly compatible? > * how can i stay out of trouble (when using postgres inside openVZ) > * who else has trouble with openVZ in combination with postgres, and > what constitutes the trouble? A quick search found this: http://forum.openvz.org/index.php?t=msg&goto=12061&&srch=postgresql+shared#msg_12061 and http://openvz.org/FAQ#User_Beancounters_.28UBC.29 > > regards, > > WBL > > -- > "Quality comes from focus and clarity of purpose" -- Mark Shuttleworth -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin