Re: WIP: Access method extendability - Mailing list pgsql-hackers

From Robert Haas
Subject Re: WIP: Access method extendability
Date
Msg-id CA+TgmoY=wTocnm_jXH3Xh92X4pOuCOoWHHMqUEzWHQMD3q5sQA@mail.gmail.com
Whole thread Raw
In response to Re: WIP: Access method extendability  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: WIP: Access method extendability
List pgsql-hackers
On Tue, Oct 28, 2014 at 10:22 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> Or put it another way, it will be easier to write new index AMs
> because we'll be able to skip the WAL part until we know we want it.

I like the feature you are proposing, but I don't think that we should
block Alexander from moving forward with a more-extensible WAL format.
I believe that's a general need even if we get the features you're
proposing, which would reduce the need for it.  After all, if somebody
builds an out-of-core index AM, ignoring WAL-logging, and then decides
that it works well enough that they want to add WAL-logging, I think
we should make that possible without requiring them to move the whole
thing in-core.

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



pgsql-hackers by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: alter user/role CURRENT_USER
Next
From: Robert Haas
Date:
Subject: Re: alter user/role CURRENT_USER