Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X9WMa-0002UA-70 for pgsql-bugs@arkaria.postgresql.org; Tue, 22 Jul 2014 09:28:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1X9WMZ-00063N-JS for pgsql-bugs@arkaria.postgresql.org; Tue, 22 Jul 2014 09:27:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1X9WMY-00063G-Kb for pgsql-bugs@postgresql.org; Tue, 22 Jul 2014 09:27:58 +0000 Received: from mail.anarazel.de ([217.115.131.40]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X9WMU-0001KJ-MY for pgsql-bugs@postgresql.org; Tue, 22 Jul 2014 09:27:57 +0000 Received: from intern.anarazel.de (p5DDC766F.dip0.t-ipconnect.de [93.220.118.111]) (Authenticated sender: andres@anarazel.de) by mail.anarazel.de (Postfix) with ESMTPSA id 2E0EF500001; Tue, 22 Jul 2014 11:27:53 +0200 (CEST) Date: Tue, 22 Jul 2014 11:27:51 +0200 From: Andres Freund To: Stuart Bishop Cc: Tom Lane , Bruce Momjian , Alvaro Herrera , PostgreSQL Bugs Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts Message-ID: <20140722092751.GF4629@alap3.anarazel.de> References: <20140619220425.GQ18688@eldon.alvh.no-ip.org> <20140620010653.GS18688@eldon.alvh.no-ip.org> <20140620180725.GD29143@momjian.us> <20140624201346.GB17110@momjian.us> <20140627210520.GP7340@eldon.alvh.no-ip.org> <20140701161419.GA16033@momjian.us> <20140701190105.GA7340@eldon.alvh.no-ip.org> <20140701193047.GB16033@momjian.us> <9879.1405877821@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org On 2014-07-22 16:08:37 +0700, Stuart Bishop wrote: > On 21 July 2014 00:37, Tom Lane wrote: > > > I'm a bit inclined to not say anything about fix procedures in the release > > notes, because I'm not sure that this is a problem in the field. If > > anybody did have a wraparound they'd be getting bleats from VACUUM, and no > > one has reported any such thing that I've heard. > > I hit the issue, but Andres helped on IRC (and so started this > thread). Yes, VACUUM failing on a production server after the 9.1->9.3 > upgrade was the problem. I'd assumed there was database corruption and > I had some unreadable blocks, and probably would have just rebuilt the > table if #postgresql hadn't been so helpful. This is actually a second problem that came up during the investigation of the problem you had - with different symptoms and causes... IIRC it's not what you've experienced. If you look at http://www.postgresql.org/docs/devel/static/release-9-3-5.html your problem should be described. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs