On 29 October 2014 09:27, Simon Riggs <si...@2ndquadrant.com> wrote: > The current system does not allow for the possibility of a corruption > bug. If one occurs, the only thing an AM can do is PANIC. It has no > mechanism to isolate the problem and deal with it, which affects the > whole server. > > So the issue is one of risk of PANIC or data loss - things we have > always taken strong measures against. That is all I have requested as > a first step. And I request it because I remember and dealt with many > bugs and user problems in earlier times of 6-9 years ago. > > You are also right: btree, GIN and GIST will benefit from this also.
Since I feel this is a real concern, I will contribute this feature, outside of the current patch. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
