Re: pg_resetwal is broken if run from v10 against older version of PG data directory
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Amit Kapila <amit.kapila16@gmail.com>,
tushar <tushar.ahuja@enterprisedb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2017-05-30T08:24:46Z
Lists: pgsql-hackers
On 29 May 2017 at 17:00, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Amit Kapila <amit.kapila16@gmail.com> writes: >> I think this happens due to commit >> f82ec32ac30ae7e3ec7c84067192535b2ff8ec0e which renames pg_xlog to >> pg_wal. It does take care of making some of the modules like >> pg_basebackup to understand both old and new directory structures, but >> not done for all the modules. > > check > >> I think we should make similar changes >> in pg_resetwal or at the very least update the docs to indicate >> pg_resetwal can give an error if used against pre-10 data directory. > > I think it's just horribly dangerous to run any version of > pg_resetxlog/pg_resetwal against any major version other than its > own. Just check the name of the directory so that pg_resetwal will refuse to run against pg_xlog directory -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Prevent running pg_resetwal/pg_resetxlog against wrong-version data dirs.
- f3db7f164a29 10.0 landed
- 9ed68f64114e 9.4.13 landed
- 98bff290747e 9.6.4 landed
- 78e4fb8e41df 9.3.18 landed
- 6b48f06da85e 9.2.22 landed
- 5bcbc4cd6d9c 9.5.8 landed
-
Rename "pg_xlog" directory to "pg_wal".
- f82ec32ac30a 10.0 cited