Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wy2hS-0005ST-Hn for pgsql-bugs@arkaria.postgresql.org; Fri, 20 Jun 2014 17:34:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Wy2hR-0003ZE-TU for pgsql-bugs@arkaria.postgresql.org; Fri, 20 Jun 2014 17:34:05 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Wy2hQ-0003Z1-Mq for pgsql-bugs@postgresql.org; Fri, 20 Jun 2014 17:34:04 +0000 Received: from smtprelay0048.b.hostedemail.com ([64.98.42.48] helo=smtprelay.b.hostedemail.com) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wy2hM-00037v-LX for pgsql-bugs@postgresql.org; Fri, 20 Jun 2014 17:34:02 +0000 Received: from filter.hostedemail.com (b-bigip1 [10.5.19.254]) by smtprelay01.b.hostedemail.com (Postfix) with ESMTP id E296B2D2A17; Fri, 20 Jun 2014 17:33:59 +0000 (UTC) X-Session-Marker: 616C76686572726540616C76682E6E6F2D69702E6F7267 X-Spam-Summary: 50, 0, 0, , d41d8cd98f00b204, alvherre@alvh.no-ip.org, :::::, RULES_HIT:41:355:379:599:967:973:988:989:1260: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:2553:2560:2563:2682:2685:2692:2693:2828:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3352:3865:3866:3867:3868:3870:3871:3872:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4605:4659:5007:6119:6261:7903:9025:9121:10004:10400:10848:11232:11256:11257:11658:11914:12296:12517:12519:12660:12740:13069:13161:13229:13311:13357:13523:13894:13895, 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:0:0 X-HE-Tag: cord99_5cdf74096553d X-Filterd-Recvd-Size: 2312 Received: from eldon.alvh.no-ip.org (unknown [186.37.27.52]) (Authenticated sender: alvherre@alvh.no-ip.org) by omf02.b.hostedemail.com (Postfix) with ESMTPA; Fri, 20 Jun 2014 17:33:58 +0000 (UTC) Received: by eldon.alvh.no-ip.org (Postfix, from userid 1000) id 90AF61FCB; Fri, 20 Jun 2014 13:33:52 -0400 (CLT) Date: Fri, 20 Jun 2014 13:33:52 -0400 From: Alvaro Herrera To: Bruce Momjian Cc: Andres Freund , PostgreSQL Bugs Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts Message-ID: <20140620173351.GV18688@eldon.alvh.no-ip.org> References: <20140619020633.GA20469@momjian.us> <20140619015205.GD3806@momjian.us> <20140619014034.GC3806@momjian.us> <20140619220425.GQ18688@eldon.alvh.no-ip.org> <20140619221240.GC27747@eldon.alvh.no-ip.org> <20140620171915.GC29143@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20140620171915.GC29143@momjian.us> User-Agent: Mutt/1.5.21 (2010-09-15) X-Pg-Spam-Score: -1.9 (-) 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 Bruce Momjian wrote: > On Thu, Jun 19, 2014 at 06:12:41PM -0400, Alvaro Herrera wrote: > > BTW I hacked up pg_resetxlog a bit to make it generate the necessary > > pg_multixact/offset file when -m is given. This is not acceptable for > > commit because it duplicates the #defines from pg_multixact.c, but maybe > > we want this functionality enough that we're interested in a more > > complete version of this patch; also it unconditionally writes one zero > > byte to the file, which is of course wrong if the file exists and > > already contains data. > > Why would we want this if the system functions fine without those files > being created? I don't think we want pg_resetxlog to be doing anything > except changing pg_controldata. I don't understand why you say the system functions fine. If you move the multixactid with pg_resetxlog to a point which doesn't have the necessary file and page, the system will not start. Only pg_upgrade knows to create the file appropriately, but normal operation doesn't. -- Álvaro Herrera 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