Re: Bug #10432 failed to re-find parent key in index

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: hlinnaka(at)iki(dot)fi, Peter Geoghegan <pg(at)heroku(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug #10432 failed to re-find parent key in index
Date: 2015-03-31 18:19:15
Message-ID: 551AE523.7030404@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 03/31/2015 10:51 AM, Andres Freund wrote:
>
> On 2015-03-31 10:49:06 -0700, Joshua D. Drake wrote:
>> On 03/31/2015 04:20 AM, Heikki Linnakangas wrote:
>>> Perhaps we could consider it after a year or two, once 9.4 is indeed
>>> very stable, but at that point you have to wonder if it's really worth
>>> the trouble anymore. If someone has runs into that issue frequently, he
>>> probably should just upgrade to 9.4.
>>
>> Ouch. That is a really poor way to look at this.
>
> Man.
>
> Easy for you to say. You're not doing the work (which would be
> significant in this case). You're not going to be blamed if the backport
> breaks more things than it fixed.

I understand that. I am not picking on anyone. I am just saying that
looking at the problem this way is poor, which it is. We are saying as a
community: Your option to remove this data loss bug is to upgrade. That
is generally not how we approach things.

JD

--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2015-03-31 18:19:40 Re: Bug #10432 failed to re-find parent key in index
Previous Message Josh Berkus 2015-03-31 18:05:55 Re: Bug #10432 failed to re-find parent key in index