Re: pg_resetwal is broken if run from v10 against older version of PG data directory

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_resetwal is broken if run from v10 against older version of PG data directory
Date: 2017-05-30 11:43:18
Message-ID: CA+TgmoYBgbfuejPqyz7y8MBnJeccvL56BOua7yxX9rN=efLyuQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 30, 2017 at 4:24 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Just check the name of the directory so that pg_resetwal will refuse
> to run against pg_xlog directory

That's a strictly weaker integrity check than what Tom already
committed. That only distinguishes pre-10 from post-10, whereas Tom
linked it to the specific major version, which is better.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-05-30 11:46:42 Re: transition table behavior with inheritance appears broken (was: Declarative partitioning - another take)
Previous Message Robert Haas 2017-05-30 11:27:12 Re: Effect of changing the value for PARALLEL_TUPLE_QUEUE_SIZE