Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XUMTO-00017y-OX for pgsql-sql@arkaria.postgresql.org; Wed, 17 Sep 2014 21:09:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XUMTO-0005eZ-4J for pgsql-sql@arkaria.postgresql.org; Wed, 17 Sep 2014 21:09:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XUMTM-0005cX-LT for pgsql-sql@postgresql.org; Wed, 17 Sep 2014 21:09:08 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XUMTI-0004T6-CK for pgsql-sql@postgresql.org; Wed, 17 Sep 2014 21:09:07 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by gateway2.nyi.internal (Postfix) with ESMTP id EC0FA20F20 for ; Wed, 17 Sep 2014 17:09:00 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 17 Sep 2014 17:09:00 -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=giZ8MajPD+9Z8lzsPt3FXGSxY3E=; b=cB45La8WfBEfwsGIdoUyORnyLP1B WZMLeKKrpXRwTAzRIFItU7t2blhn+qPaGr+2znkZ/15vvZBCtDH4aoBpG7F+J5xt qJNg1hlHyfKc0X5wUnrGbBNOm0We3v/bBJB/4RGXWlLcxwvBECpeXmh2zvxDF9yR mHm+rGzrPl0u0nI= 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=giZ8MajPD+9Z8lzsPt3FXG SxY3E=; b=sLyQRfpv3z1FSok7AHheOxi5hFShm5HtWfMIMIIN7R8m1Ij+ykx7Nh aM3qIB7czUQH6Ri+Kz0cRcHo+sKwF4n7XyVZBkeSgvzFewi2wJpYC2V1et/i7UKn y4wvi2v++yklCsCB+bhTFFgBHBcLsdOCypTQ3iHwc9o7f0DCh0RlM= X-Sasl-enc: FuDkIHgIdzxu17x33ya5Avc5f2aDoHCL1cjidRsiGLfC 1410988140 Received: from [192.168.1.5] (unknown [174.21.177.1]) by mail.messagingengine.com (Postfix) with ESMTPA id 5C1DDC00921; Wed, 17 Sep 2014 17:09:00 -0400 (EDT) Message-ID: <5419F86B.3000403@aklaver.com> Date: Wed, 17 Sep 2014 14:08:59 -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: 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-sql Precedence: bulk Sender: pgsql-sql-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? Now I am moving into the deep water:) Could the first item under Changes in the link below apply?: http://www.postgresql.org/docs/current/static/release-9-3-5.html > > Regards... -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql