agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: Andres Freund <andres@2ndquadrant.com>
To: Dev Kumkar <devdas.kumkar@gmail.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] pg_multixact issues
Date: Thu, 18 Sep 2014 12:33:38 +0200
Message-ID: <20140918103338.GF17265@alap3.anarazel.de> (raw)
In-Reply-To: <CALSLE1NT9c9eYs95Q3=7C5dWkzrrULQTy6bcSkFsP1OKA+AXHg@mail.gmail.com>
References: <CALSLE1P4knmyFa5BzdeYo7fVnjw-1-TwW9dXTEW-9nJjK4fQMg@mail.gmail.com>
<54198AEB.2070508@aklaver.com>
<CALSLE1Pywi4SAyvOVHn+FfxTHMF88t4esgPXxwS9etWMzeE0Rg@mail.gmail.com>
<CALSLE1MAgy4QC0-xLju6MBxO6Upp6=84xwAMt2dkfiGbd6pB9Q@mail.gmail.com>
<5419F908.2080303@aklaver.com>
<CALSLE1NT9c9eYs95Q3=7C5dWkzrrULQTy6bcSkFsP1OKA+AXHg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
On 2014-09-18 14:41:07 +0530, Dev Kumkar wrote:
> On Thu, Sep 18, 2014 at 2:41 AM, Adrian Klaver <adrian.klaver@aklaver.com>
> 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
view thread (24+ messages) latest in thread
Message-ID: <20140918103338.GF17265@alap3.anarazel.de>
Permalink: ../20140918103338.GF17265@alap3.anarazel.de/
Also on: postgresql.org/message-id/20140918103338.GF17265@alap3.anarazel.de
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: andres@2ndquadrant.com, devdas.kumkar@gmail.com, adrian.klaver@aklaver.com, pgsql-general@postgresql.org
Subject: Re: [SQL] pg_multixact issues
In-Reply-To: <20140918103338.GF17265@alap3.anarazel.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox