Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XUMVt-0001Gu-Ew for pgsql-general@arkaria.postgresql.org; Wed, 17 Sep 2014 21:11:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XUMVs-0000Lc-2q for pgsql-general@arkaria.postgresql.org; Wed, 17 Sep 2014 21:11:44 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XUMVq-0000It-IC for pgsql-general@postgresql.org; Wed, 17 Sep 2014 21:11:42 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XUMVn-0004fJ-Bh for pgsql-general@postgresql.org; Wed, 17 Sep 2014 21:11:40 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by gateway2.nyi.internal (Postfix) with ESMTP id 9C8E82104E for ; Wed, 17 Sep 2014 17:11:37 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Wed, 17 Sep 2014 17:11:37 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=3ZIDaTxoFs7aDNQFTcVtu9Oo3as=; b=BRK8qtbMTS1+f/ET6NV8+t1wneOE oa4Jd/z7m/IvnpcIg+lTVtyQZCpXTi4E34hVSt8KwKe2fxsgkiiqchJMWZ7GCBBB s26s2HDH25XfQLUT8SdT1RvLqWNIQ4xOf8UUm/6XRWxMXL1llOEdoERHx5aR4zsZ vawTbECy8q5zTvE= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=3ZIDaTxoFs7aDNQFTcVtu9 Oo3as=; b=GyRH3Im5eX+frzIzGpX9aM0HA+u6VlwW78yjoR5+eN2+2tt2J020c7 JE+l7qz/Qla997szugBQrgBjEDH+c2ZeVs0w3roiGFPrUcdouAN0wjeNAIcQqJb1 Im5HAp9t77g+TGJhoOJZqRywT0XRiLaKMjAwhBe7eJOJSiIWuOeMY= X-Sasl-enc: JCxy7rff+6JoX+f7ro0XTndMaQtwNnKs2sjAbkJ2S2mQ 1410988297 Received: from [192.168.1.5] (unknown [174.21.177.1]) by mail.messagingengine.com (Postfix) with ESMTPA id 08791C00918; Wed, 17 Sep 2014 17:11:36 -0400 (EDT) Message-ID: <5419F908.2080303@aklaver.com> Date: Wed, 17 Sep 2014 14:11:36 -0700 From: Adrian Klaver User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Dev Kumkar CC: "pgsql-general@postgresql.org" , pgsql-sql@postgresql.org Subject: Re: [SQL] pg_multixact issues References: <54198AEB.2070508@aklaver.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org On 09/17/2014 01:36 PM, Dev Kumkar wrote: > On Wed, Sep 17, 2014 at 7:20 PM, Dev Kumkar > wrote: > > On Wed, Sep 17, 2014 at 6:51 PM, Adrian Klaver > > wrote: > > > http://www.postgresql.org/__docs/9.3/static/routine-__vacuuming.html#VACUUM-FOR-__MULTIXACT-WRAPAROUND > > > > Looked into these details. Can there be an example explained that will > really help to understand this in practice? > > Also one additional information here, the database was restarted various > times. But still the pg_multixact directory size is increasing. > Actually there were multiple updates happening in different processes > which lead to the locking issues and landed up into this situation. > > How can I recover the system at this stage and also clean up > pg_multixact gracefully? Aaah, hit enter too soon. Also see the other changes under Changes that apply to multixact in 9.3.5 > > Regards... -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general