Date: Fri, 22 Nov 2013 12:18:20 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Karl Hafner <karl@scoreloop.com>
Cc: pgsql-admin@postgresql.org,
 Strahinja =?utf-8?B?S3VzdHVkacSH?= <strahinjak@nordeus.com>
Subject: Re: 
Message-ID: <20131122151820.GM6041@eldon.alvh.no-ip.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CA+MJ4cRdt__yBCGhz2pqhAZ+1WLRTKZ-afJi0ZPBT-ti-YUVtw@mail.gmail.com>
 <CA+MJ4cS6Q4RKf4WD1sKmjwhCEkM5wN5gZfXpAGUbrZ2dauTGqA@mail.gmail.com>
 <CA+MJ4cS1bdt6eGbXuhLFXVQHfrn6pyyHMHp_P1vh71TPrVi+UA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Hi,

Karl Hafner wrote:

> I am currently worried about an error that shows up in our log files since
> a few weeks:
> 
> 2013-11-15 07:13:13 UTC [22668]: [2-1] ERROR:  MultiXactId 2683601542 does
> no longer exist -- apparent wraparound
> 2013-11-15 07:13:13 UTC [22668]: [3-1] CONTEXT:  automatic vacuum of table
> "scoreloop.public.gamer_device_sightings"

So you're running 9.3.

Can you please share the output of pg_controldata and a directory
listing of pg_multixact/offsets?

> Since the autovacuum process is failing each time because of: "ERROR:
>  MultiXactId 2683601542 does no longer exist -- apparent wraparound", I
> have expected the manual vacuum also to fail because of the same error.
> I've tried it anyway. Well ... manual vacuum also fails unfortunately.

Yeah, it's unlikely a manual vacuum (of either kind) would succeed.  

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin