Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XUZ2F-00018o-7H for pgsql-general@arkaria.postgresql.org; Thu, 18 Sep 2014 10:33:59 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XUZ2E-0001qQ-CF for pgsql-general@arkaria.postgresql.org; Thu, 18 Sep 2014 10:33:58 +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 1XUZ2C-0001qA-0P; Thu, 18 Sep 2014 10:33:56 +0000 Received: from mail.anarazel.de ([217.115.131.40]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XUZ1z-0002aU-Ji; Thu, 18 Sep 2014 10:33:54 +0000 Received: from intern.anarazel.de (p5DDC48DE.dip0.t-ipconnect.de [93.220.72.222]) (Authenticated sender: andres@anarazel.de) by mail.anarazel.de (Postfix) with ESMTPSA id 67629520004; Thu, 18 Sep 2014 12:33:39 +0200 (CEST) Date: Thu, 18 Sep 2014 12:33:38 +0200 From: Andres Freund To: Dev Kumkar Cc: Adrian Klaver , "pgsql-general@postgresql.org" , pgsql-sql@postgresql.org Subject: Re: [SQL] pg_multixact issues Message-ID: <20140918103338.GF17265@alap3.anarazel.de> References: <54198AEB.2070508@aklaver.com> <5419F908.2080303@aklaver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Pg-Spam-Score: -2.6 (--) 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 2014-09-18 14:41:07 +0530, Dev Kumkar wrote: > On Thu, Sep 18, 2014 at 2:41 AM, Adrian Klaver > wrote: > > > > > Aaah, hit enter too soon. Also see the other changes under Changes that > > apply to multixact in 9.3.5 > > > Thanks for sharing same. Found this one interesting "Truncate pg_multixact > during checkpoints, not during VACUUM (Álvaro Herrera)" and also other > changes. But am not sure are you suggesting to move to 9.3.5 ? I don't think that's relevant for you. Did you upgrade the database using pg_upgrade? > Actually looking for some guidelines on truncating pg_multixact at this > situation. > > - Do I need to run vaccum manually here and then the pg_multixact can be > truncated? > - Actually looking out for some hints wherein can know the current > pg_multixact/members which are active and which one are stale which can be > truncated? Is there any query to find this information? > > pg_class.relminmxid can be referred but should I change the value of > autovacuum_multixact_freeze_max_age which defaults to 400 million > multixacts, setting this value to lower limits would help in cleaning up > pg_multixact? Can you show pg_controldata output and the output of 'SELECT oid, datname, relfrozenxid, age(relfrozenxid), relminmxid FROM pg_database;'? Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general