Re: MultiXactId Error in Autovacuum

From: Karl Hafner <karl(at)scoreloop(dot)com>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: Strahinja Kustudic <strahinjak(at)nordeus(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: MultiXactId Error in Autovacuum
Date: 2013-11-19 11:14:44
Message-ID: CA+MJ4cTqPEn1f4irCTM4d71E0YrBZTKfcmnJ6y9DPVSHSkXCDQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi Laurenz,

thank you for looking into my issue.

Do you know if you experienced transaction ID wraparound as the
> message suggests?
>

I am not aware of a wraparound in the past. I am quite sure no.

Are there any other questionable messages in the log?
>

The log shows nothing special except this error that is always associated
with the same MultiXactId 2683601542.

>
> What do you get for the following queries:
>
> SELECT txid_current();
>

txid_current
--------------
1673482898

>
> SELECT datname, datfrozenxid FROM pg_database;
>

SELECT datname, datfrozenxid FROM pg_database;

datname | datfrozenxid
-----------+--------------
postgres | 1497699916
template0 | 1497699916
MYDB | 1335927866
template1 | 1497699916

>
> SELECT current_setting('autovacuum_freeze_max_age'),
> current_setting('vacuum_freeze_min_age'),
> current_setting('vacuum_freeze_table_age');
>
>
current_setting | current_setting | current_setting
-----------------+-----------------+-----------------
200000000 | 50000000 | 150000000

Thank you!
Best regards,
Karl

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Luca Ferrari 2013-11-19 11:59:54 Re: How to install pgagent on linux?
Previous Message Gary Stainburn 2013-11-19 11:08:18 Postgresql not accessible, recovering