Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dFRyD-0002VZ-Cc for pgsql-hackers@arkaria.postgresql.org; Mon, 29 May 2017 21:12:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dFRyC-0006Ij-Qm for pgsql-hackers@arkaria.postgresql.org; Mon, 29 May 2017 21:12:56 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dFRyB-0006HV-Go for pgsql-hackers@postgresql.org; Mon, 29 May 2017 21:12:55 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dFRy9-0008Mx-6F for pgsql-hackers@postgresql.org; Mon, 29 May 2017 21:12:54 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v4TLCpt8001792; Mon, 29 May 2017 17:12:51 -0400 From: Tom Lane To: Michael Paquier cc: Amit Kapila , tushar , PostgreSQL-development Subject: Re: pg_resetwal is broken if run from v10 against older version of PG data directory In-reply-to: References: <11442.1496073654@sss.pgh.pa.us> Comments: In-reply-to Michael Paquier message dated "Mon, 29 May 2017 09:55:26 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1790.1496092371.1@sss.pgh.pa.us> Date: Mon, 29 May 2017 17:12:51 -0400 Message-ID: <1791.1496092371@sss.pgh.pa.us> 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 Michael Paquier writes: > Agreed. Shouldn't this be back-patched? PG_CONTROL_VERSION has not > been bumped between 9.4 and 9.5. Attached is a patch for HEAD. Pushed with minor adjustments. Notably, I didn't take your addition of canonicalize_path() and referencing the file by absolute path. That seems like an independent and rather debatable behavioral change. All the other files that pg_resetwal touches are referenced with relative paths; if we did want to change the reporting, shouldn't we change it for all of them? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers