RE: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory - Mailing list pgsql-hackers

From Takashi Menjo
Subject RE: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory
Date
Msg-id 000501d4b48b$4acba1a0$e062e4e0$@lab.ntt.co.jp
Whole thread Raw
In response to Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistentmemory  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistentmemory  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Hello,


On behalf of Yoshimi, I rebased the patchset onto the latest master
(e3565fd6).
Please see the attachment. It also includes an additional bug fix (in patch
0002) 
about temporary filename.

Note that PMDK 1.4.2+ supports MAP_SYNC and MAP_SHARED_VALIDATE flags, 
so please use a new version of PMDK when you test. The latest version is
1.5.


Heikki Linnakangas wrote:
> To re-iterate what I said earlier in this thread, I think the next step 
> here is to write a patch that modifies xlog.c to use plain old 
> mmap()/msync() to memory-map the WAL files, to replace the WAL buffers.

Sorry but my new patchset still uses PMDK, because PMDK is supported on
Linux 
_and Windows_, and I think someone may want to test this patchset on
Windows...


Regards,
Takashi

-- 
Takashi Menjo - NTT Software Innovation Center
<menjo.takashi@lab.ntt.co.jp>


Attachment

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal - plpgsql unique statement id
Next
From: Michael Paquier
Date:
Subject: Re: Simplify set of flags used by MyXactFlags