Re: WIP: Access method extendability
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Andres Freund <andres@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Stephen Frost <sfrost@snowman.net>,
Alexander Korotkov <aekorotkov@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2014-10-29T18:28:08Z
Lists: pgsql-hackers
On 29 October 2014 09:27, Simon Riggs <simon@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
Commits
-
Support CREATE ACCESS METHOD
- 473b93287040 9.6.0 landed
-
Restructure index access method API to hide most of it at the C level.
- 65c5fcd353a8 9.6.0 cited