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

From: Takashi Menjo <takashi(dot)menjo(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Takashi Menjo <takashi(dot)menjou(dot)vg(at)hco(dot)ntt(dot)co(dot)jp>, Teruaki Ishizaki <teruaki(dot)ishizaki(dot)ph(at)hco(dot)ntt(dot)co(dot)jp>
Subject: Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory
Date: 2021-02-17 05:13:06
Message-ID: CAOwnP3O3O1GbHpddUAzT=CP3aMpX99=1WtBAfsRZYe2Ui53MFQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rebased to make patchset v5.

I also found that my past replies have separated the thread in the
pgsql-hackers archive. I try to connect this mail to the original
thread [1], and let this point to the separated portions [2][3][4].
Note that the patchset v3 is in [3] and v4 is in [4].

Regards,

[1] https://www.postgresql.org/message-id/flat/C20D38E97BCB33DAD59E3A1%40lab.ntt.co.jp
[2] https://www.postgresql.org/message-id/flat/000501d4b794%245094d140%24f1be73c0%24%40lab.ntt.co.jp
[3] https://www.postgresql.org/message-id/flat/000001d4b863%244c9e8fc0%24e5dbaf40%24%40lab.ntt.co.jp
[4] https://www.postgresql.org/message-id/flat/000001d4c2a1%2488c6cc40%249a5464c0%24%40lab.ntt.co.jp

--
Takashi Menjo <takashi(dot)menjo(at)gmail(dot)com>

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2021-02-17 05:40:32 Re: [POC] verifying UTF-8 using SIMD instructions
Previous Message Michael Paquier 2021-02-17 04:52:09 Re: ERROR: invalid spinlock number: 0