Re: [HACKERS] Pluggable storage - Mailing list pgsql-hackers

From David Steele
Subject Re: [HACKERS] Pluggable storage
Date
Msg-id 935d4bc2-936e-73ff-b242-d2e8ebfc5d55@pgmasters.net
Whole thread Raw
In response to Re: [HACKERS] Pluggable storage  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Responses Re: [HACKERS] Pluggable storage  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2/26/18 3:19 AM, Alexander Korotkov wrote:
> On Fri, Feb 23, 2018 at 2:20 AM, Robert Haas <robertmhaas@gmail.com
> <mailto:robertmhaas@gmail.com>> wrote:
> 
>     On Fri, Feb 16, 2018 at 5:56 AM, Alexander Korotkov
>     <a.korotkov@postgrespro.ru <mailto:a.korotkov@postgrespro.ru>> wrote:
>     > BTW, EnterpriseDB announces zheap table access method (heap with undo log)
>     > [2].  I think this is great, and I'm looking forward for publishing zheap in
>     > mailing lists.  But I'm concerning about its compatibility with pluggable
>     > table access methods API.  Does zheap use table AM API from this thread?  Or
>     > does it just override current heap and needs to be adopted to use table AM
>     > API?  Or does it implements own API?
> 
>     Right now it just hacks the code.  The plan is to adapt it to whatever
>     API we settle on in this thread.
> 
> 
> Great, thank you for clarification.  I'm looking forward reviewing zheap :)
I think this entry should be moved the the next CF.  I'll do that
tomorrow unless there are objections.

Regards,
-- 
-David
david@pgmasters.net


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [HACKERS] [PATCH] Incremental sort
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Restrict concurrent update/delete with UPDATE ofpartition key