Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YxGPC-0006aA-CC for pgsql-hackers@arkaria.postgresql.org; Tue, 26 May 2015 15:04:34 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YxGPB-0007g3-MB for pgsql-hackers@arkaria.postgresql.org; Tue, 26 May 2015 15:04:33 +0000 Received: from makus.postgresql.org ([174.143.35.229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YxGP1-0007OM-AY for pgsql-hackers@postgresql.org; Tue, 26 May 2015 15:04:23 +0000 Received: from smtprelay0126.b.hostedemail.com ([64.98.42.126] helo=smtprelay.b.hostedemail.com) by makus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1YxGMr-0000nw-LZ for pgsql-hackers@postgresql.org; Tue, 26 May 2015 15:02:13 +0000 Received: from filter.hostedemail.com (10.5.19.248.rfc1918.com [10.5.19.248]) by smtprelay06.b.hostedemail.com (Postfix) with ESMTP id E26E98D238; Tue, 26 May 2015 15:02:08 +0000 (UTC) X-Session-Marker: 616C76686572726540616C76682E6E6F2D69702E6F7267 X-Spam-Summary: 13, 1.2, 0, , d41d8cd98f00b204, alvherre@alvh.no-ip.org, :::, RULES_HIT:41:355:379:599:967:973:988:989:1260:1263:1277:1311:1312:1313:1314:1345:1359:1437:1515:1516:1518:1519:1534:1541:1593:1594:1595:1596:1711:1730:1747:1777:1792:2393:2525:2560:2563:2682:2685:2828:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3353:3865:3867:3868:3871:3872:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4250:4321:4605:4659:5007:6238:6261:7875:7901:8957:9025:9121:10008:10400:10450:10455:10483:10848:11026:11232:11256:11257:11473:11638:11658:11914:12296:12517:12519:12555:12663:13069:13255:13311:13357:13894:13895:19901:19904:19997:19999:21080, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:none, Custom_rules:0:1:0 X-HE-Tag: burst51_4ccffd5554e63 X-Filterd-Recvd-Size: 2232 Received: from alvin.alvh.no-ip.org (unknown [181.43.8.209]) (Authenticated sender: alvherre@alvh.no-ip.org) by omf02.b.hostedemail.com (Postfix) with ESMTPA; Tue, 26 May 2015 15:02:07 +0000 (UTC) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id BA41E66A; Tue, 26 May 2015 12:01:59 -0300 (CLT) Date: Tue, 26 May 2015 12:01:59 -0300 From: Alvaro Herrera To: Paul Smith Cc: pgsql-hackers@postgresql.org Subject: Re: ERROR: MultiXactId xxxx has not been created yet -- apparent wraparound Message-ID: <20150526150159.GV5885@postgresql.org> References: <556439CF.7070109@pscs.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <556439CF.7070109@pscs.co.uk> User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Paul Smith wrote: > With PostgreSQL 9.3.5 on Ubuntu 12.04, I'm getting the error: > > ERROR: MultiXactId 1934308693 has not been created yet -- apparent > wraparound > > on doing various queries on our database. I don't think it is a wraparound - > I think the tuple has mistakenly decided it has a MultiXactId related to it. Yeah, that looks like the case. According to your pg_controldata output, you haven't used many multixacts at all: > Latest checkpoint's NextMultiXactId: 216 > Latest checkpoint's NextMultiOffset: 439 and the fact that you only have these files: > The pg_multixact directory contains two files > members/0000 > offsets/0000 confirms this. You XID counter is also rather low, only 24 million: > Latest checkpoint's NextXID: 0/24005839 so it doesn't seem plausible that the single bit HEAP_XMAX_IS_MULTI was turned on accidentally (something which I've never seen happen). It doesn't look like a randomly corrupt page either; normally you would see errors about mismatching page headers before you get to the point where Xmax is read. I wonder if the data page came from elsewhere. Maybe you copied a data file from another database? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers