Re: Did we really want to force an initdb in beta2? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Did we really want to force an initdb in beta2?
Date
Msg-id AANLkTileUZTfali3DrozPTqjCzpuWljLRKWDd2Klkz4f@mail.gmail.com
Whole thread Raw
In response to Re: Did we really want to force an initdb in beta2?  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Thu, Jun 3, 2010 at 11:25 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> On 03/06/10 17:54, Tom Lane wrote:
>>
>> Because that's the consequences of fooling with pg_control.
>> I committed the PG_CONTROL_VERSION bump that was missing from
>> the patch Robert committed last night, but I wonder whether
>> we shouldn't revert the whole thing instead.  It's not apparent
>> to me that what it bought is worth forcing beta testers to initdb.
>
> Hmph, good point, I did not think of that at all when I reviewed the patch.
>
> If we moved the new DB_SHUTDOWNED_IN_RECOVERY as the last item in the enum,
> we would stay backwards-compatible.

Ugh, sorry about that.  I didn't realize this either.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: functional call named notation clashes with SQL feature
Next
From: Tom Lane
Date:
Subject: Re: Keepalive for max_standby_delay