On 29 May 2017 at 17:00, Tom Lane <[email protected]> wrote: > Amit Kapila <[email protected]> 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 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
