RE: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory

From: "Takashi Menjo" <menjo(dot)takashi(at)lab(dot)ntt(dot)co(dot)jp>
To: "'Heikki Linnakangas'" <hlinnaka(at)iki(dot)fi>
Cc: "'Andres Freund'" <andres(at)anarazel(dot)de>, "'Michael Paquier'" <michael(at)paquier(dot)xyz>, "'Dmitry Dolgov'" <9erthalion6(at)gmail(dot)com>, <ishizaki(dot)teruaki(at)lab(dot)ntt(dot)co(dot)jp>, <ichiyanagi(dot)yoshimi(at)lab(dot)ntt(dot)co(dot)jp>, <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory
Date: 2019-01-25 08:52:24
Message-ID: 000501d4b48b$4acba1a0$e062e4e0$@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: 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(dot)takashi(at)lab(dot)ntt(dot)co(dot)jp>

Attachment Content-Type Size
0001-Add-configure-option-for-PMDK-v2.patch application/octet-stream 5.0 KB
0002-Read-write-WAL-files-using-PMDK-v2.patch application/octet-stream 46.1 KB
0003-Walreceiver-WAL-IO-using-PMDK-v2.patch application/octet-stream 4.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-01-25 10:19:32 Re: Simplify set of flags used by MyXactFlags
Previous Message Pavel Stehule 2019-01-25 08:44:28 Re: proposal - plpgsql unique statement id