Re: Version number for pg_control

From: David Steele <david(at)pgmasters(dot)net>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Version number for pg_control
Date: 2016-07-15 22:24:25
Message-ID: 3f62ff22-9b82-8324-8a1f-fe09e2a2736b@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/15/16 6:13 PM, Alvaro Herrera wrote:
> David Steele wrote:
>> On 7/15/16 5:47 PM, Alvaro Herrera wrote:
>
>>> I can't quite make up my mind about it. It seems pointless to change
>>> it now, but at the same time it seems wrong to let it continue to be
>>> unchanged from 9.4.
>>>
>>> I slightly lean towards changing it in 9.6.
>>
>> +1 for changing it. However, I don't think it's such a big deal since
>> each version since 8.3 (at least) has had a unique catalog version.
>>
>> Maybe this would affect pg_controldata or other supporting utilities but
>> the server itself should not be affected since it also checks the
>> catalog version.
>
> I didn't verify pg_resetxlog behavior, but hypothetically running 9.4's
> on a 9.5 installation would result in a broken pg_control file.

Yuck. I think of the utilities as read-only but there are obviously
some notable exceptions.

So +2 for this change. Why propagate that mess into the future?

--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-07-15 22:51:16 Re: Version number for pg_control
Previous Message Tom Lane 2016-07-15 22:22:23 Re: Version number for pg_control