On Tue, Sep 30, 2014 at 8:50 PM, Alvaro Herrera
wrote:
> Did you try decreasing the autovacuum_multixact_freeze_min_age and
> autovacuum_multixact_freeze_table_age parameters?
>
As per the docs this set anywhere from zero to 1 billion for
vacuum_multixact_freeze_min_age
And zero to 2 billion for
Dev Kumkar wrote:
> On Fri, Sep 26, 2014 at 1:36 PM, Dev Kumkar 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 da
On Fri, Sep 26, 2014 at 1:36 PM, Dev Kumkar 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. Ho
On Fri, Sep 19, 2014 at 1:23 PM, Dev Kumkar wrote:
> Apologies for the delay, was working/troubleshooting same issue and was
> away from my emails. :(
> Regards...
>
Received the database with huge pg_multixact directory of size 21G and
there are ~82,000 files in "pg_multixact/members" and 202 f
On Fri, Sep 19, 2014 at 1:03 PM, Andres Freund
wrote:
> Yes: Learning some patience. You'd given the previous answer two hours
> before this one. Nobody is paid to work on this list...
Apologies for the delay, was working/troubleshooting same issue and was
away from my emails. :(
Regards...
On Fri, Sep 19, 2014 at 8:07 AM, Alvaro Herrera
wrote:
> Can you paste the pg_controldata output please?
>
pg_controldata output as follows:
pg_control version number:937
Catalog version number: 201306121
Database system identifier: 6023658189132429183
Databa
On 2014-09-18 22:52:57 +0530, Dev Kumkar wrote:
> On Thu, Sep 18, 2014 at 6:20 PM, Dev Kumkar wrote:
>
> > On Thu, Sep 18, 2014 at 4:03 PM, Andres Freund
> > wrote:
> >
> >> I don't think that's relevant for you.
> >>
> >> Did you upgrade the database using pg_upgrade?
> >>
> >
> > That's correc
Dev Kumkar wrote:
> On Thu, Sep 18, 2014 at 4:03 PM, Andres Freund
> wrote:
> > Can you show pg_controldata output and the output of 'SELECT oid,
> > datname, relfrozenxid, age(relfrozenxid), relminmxid FROM pg_database;'?
> >
>
> Here are the details:
> oid datname datfrozenxidag
On 09/18/2014 10:22 AM, Dev Kumkar wrote:
On Thu, Sep 18, 2014 at 6:20 PM, Dev Kumkar mailto:devdas.kum...@gmail.com>> wrote:
On Thu, Sep 18, 2014 at 4:03 PM, Andres Freund
mailto:and...@2ndquadrant.com>> wrote:
I don't think that's relevant for you.
Did you upgrade the
On Thu, Sep 18, 2014 at 6:20 PM, Dev Kumkar wrote:
> On Thu, Sep 18, 2014 at 4:03 PM, Andres Freund
> wrote:
>
>> I don't think that's relevant for you.
>>
>> Did you upgrade the database using pg_upgrade?
>>
>
> That's correct! No, there is no upgrade here.
>
>
>> Can you show pg_controldata ou
On Thu, Sep 18, 2014 at 4:03 PM, Andres Freund
wrote:
> I don't think that's relevant for you.
>
> Did you upgrade the database using pg_upgrade?
>
That's correct! No, there is no upgrade here.
> Can you show pg_controldata output and the output of 'SELECT oid,
> datname, relfrozenxid, age(rel
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_mult
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
On 09/17/2014 01:36 PM, Dev Kumkar wrote:
On Wed, Sep 17, 2014 at 7:20 PM, Dev Kumkar mailto:devdas.kum...@gmail.com>> wrote:
On Wed, Sep 17, 2014 at 6:51 PM, Adrian Klaver
mailto:adrian.kla...@aklaver.com>> wrote:
http://www.postgresql.org/__docs/9.3/static/routine-__vacuumin
On 09/17/2014 01:36 PM, Dev Kumkar wrote:
On Wed, Sep 17, 2014 at 7:20 PM, Dev Kumkar mailto:devdas.kum...@gmail.com>> wrote:
On Wed, Sep 17, 2014 at 6:51 PM, Adrian Klaver
mailto:adrian.kla...@aklaver.com>> wrote:
http://www.postgresql.org/__docs/9.3/static/routine-__vacuumin
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
re
On Wed, Sep 17, 2014 at 7:20 PM, Dev Kumkar wrote:
> Thanks, yes have been looking into pg_stat_activity table and somehow the
> standard queries are hanging.
> Not sure if this is because the database response has become very slow.
>
Would having a huge pg_multixact directory have an impact on
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
>
> 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/sta
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_multixactSubdirectory containing mu
19 matches
Mail list logo
