Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XUFBH-0000L4-Lx for pgsql-sql@arkaria.postgresql.org; Wed, 17 Sep 2014 13:22:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XUFBH-0004nT-4z for pgsql-sql@arkaria.postgresql.org; Wed, 17 Sep 2014 13:21:59 +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 1XUFBF-0004kK-5t for pgsql-sql@postgresql.org; Wed, 17 Sep 2014 13:21:57 +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 1XUFB8-0000aT-5Q for pgsql-sql@postgresql.org; Wed, 17 Sep 2014 13:21:55 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by gateway2.nyi.internal (Postfix) with ESMTP id 66F8420F46 for ; Wed, 17 Sep 2014 09:21:48 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 17 Sep 2014 09:21:48 -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=mxSDxitbr5WQyDV4IAdvOHEQ8gU=; b=eZBZ56cQlGgk4B1uz/hckZbOMgpc JlHH+w9C+PpGVvGwLSR01QjnSnRptHpiDqSBqONnPk8VObefVJGMDaFfIueqCaaL F0hmKFdl7Ng7mWfk+z/wo7TR69yDOf/nZ3YxoPyP+hEf8kpf2c7IlQM8Fldw60Ww 5XaYu8LHojAmixM= 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=mxSDxitbr5WQyDV4IAdvOH EQ8gU=; b=MnRqZ6C0bckJWdAx2idLvjRGkhDJavVR9XBZGm+Lre/MGfNu08VJDz O9GTZVGmEgzh54HAFXtXXqUf7idOe0euk1Jd/sDDJJ03auaimYV7cDJLNG9K3rsv PxLnlbfgzdWsSs2I7wh2vxu0AUTuCsTUAaf9ytcP0aULPe5h/yoPQ= X-Sasl-enc: lWVeAThTFoIOndjoFY/oj1I70jhCagx93epA9DCVplcX 1410960108 Received: from [192.168.1.5] (unknown [174.21.177.1]) by mail.messagingengine.com (Postfix) with ESMTPA id CC1CF6801B2; Wed, 17 Sep 2014 09:21:47 -0400 (EDT) Message-ID: <54198AEB.2070508@aklaver.com> Date: Wed, 17 Sep 2014 06:21:47 -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 , "pgsql-general@postgresql.org" , pgsql-sql@postgresql.org Subject: Re: pg_multixact issues References: 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 05:16 AM, Dev Kumkar wrote: > > Hello, > > On one my machine the pg_multixact directory size has grown up to 5 GB > and am not sure how to clean up this directory. > > From the storage-file-layout this directory contains multitransaction > status data. > pg_multixact Subdirectory containing multitransaction status data (used > for shared row locks) > > > It would really help if someone can provide some reading material > regarding pg_multixact? Would this also result in database slowness by > any chance? > > Are there any tweaking commands related to this directory settings, also > how can I cleanup/truncate this directory without impacting the overall > database. http://www.postgresql.org/docs/9.3/static/routine-vacuuming.html#VACUUM-FOR-MULTIXACT-WRAPAROUND Might also want to take a look at pg_stat_activity to see what queries maybe hanging up: http://www.postgresql.org/docs/9.3/static/monitoring-stats.html#PG-STAT-ACTIVITY-VIEW > > Looking forward to get some insight here. > > 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