Date: Tue, 30 Sep 2014 12:20:13 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Dev Kumkar <devdas.kumkar@gmail.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>,
 "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: Re: [SQL] pg_multixact issues
Message-ID: <20140930152013.GO5311@eldon.alvh.no-ip.org>
References: 
 <CALSLE1MAgy4QC0-xLju6MBxO6Upp6=84xwAMt2dkfiGbd6pB9Q@mail.gmail.com>
 <5419F908.2080303@aklaver.com>
 <CALSLE1NT9c9eYs95Q3=7C5dWkzrrULQTy6bcSkFsP1OKA+AXHg@mail.gmail.com>
 <20140918103338.GF17265@alap3.anarazel.de>
 <CALSLE1Mngj=vyA-hdKaB-HWQ=gU_A3vDRE4ddyKwViTRFXmLFg@mail.gmail.com>
 <CALSLE1OmAcaj6BmHu07LWNkRgd=xvoHyqsasTTVquHxXcni-mg@mail.gmail.com>
 <20140919073357.GA4277@alap3.anarazel.de>
 <CALSLE1Pq5Xcz0y7c-C1c05zVo+8B+HnB8iyzRVUASHqO2vyVmQ@mail.gmail.com>
 <CALSLE1Pe22dK8ULkGEQd3X3jOrA32Xs2zkxU2OAaUOTU4z+a0Q@mail.gmail.com>
 <CALSLE1PzxeRd0RAmC20-X01TijiR-aSjxAVjfze6keW_iYMdCA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CALSLE1PzxeRd0RAmC20-X01TijiR-aSjxAVjfze6keW_iYMdCA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk
Sender: pgsql-general-owner@postgresql.org

Dev Kumkar wrote:
> On Fri, Sep 26, 2014 at 1:36 PM, Dev Kumkar <devdas.kumkar@gmail.com> wrote:
> 
> > Received the database with huge pg_multixact directory of size 21G and
> > there are ~82,000 files in "pg_multixact/members" and 202 files in
> > "pg_multixact/offsets" directory.
> >
> > Did run "vacuum full" on this database and it was successful. However now
> > am not sure about pg_multixact directory. truncating this directory except
> > 0000 file results into database start up issues, of course this is not
> > correct way of truncating.
> >          FATAL:  could not access status of transaction 13224692
> >
> > Stumped ! Please provide some comments on how to truncate pg_multixact
> > files and if there is any impact because of these files on database
> > performance.
> >
> 
> Facing this issue on couple more machines where pg_multixact is huge and
> not being cleaned up. Any suggestions / troubleshooting tips?

Did you try decreasing the autovacuum_multixact_freeze_min_age and
autovacuum_multixact_freeze_table_age parameters?

What exact server version are you running?

-- 
Álvaro Herrera                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