Re: FSM corruption leading to errors

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FSM corruption leading to errors
Date: 2016-10-19 13:14:39
Message-ID: b7d4ebfb-84c1-b0de-42b4-3b8a6e9dab02@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/19/2016 02:32 PM, Heikki Linnakangas wrote:
> On 10/19/2016 02:29 PM, Heikki Linnakangas wrote:
>> On 10/19/2016 01:07 PM, Pavan Deolasee wrote:
>>> Anyways, we seem good to go with the patch.
>>
>> Ok, committed. Thanks for the analysis!
>
> Oh, forgot that this needs to be backported, of course. Will do that
> shortly...

Done.

This didn't include anything to cope with an already-corrupt FSM, BTW.
Do we still want to try something for that? I think it's good enough if
we prevent the FSM corruption from happening, but not sure what the
consensus on that might be..

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2016-10-19 13:21:31 Re: Using pg_ctl promote -w in TAP tests
Previous Message Robert Haas 2016-10-19 13:00:06 Re: Remove vacuum_defer_cleanup_age