| From: | "Takashi Menjo" <menjo(dot)takashi(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| 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>, <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-29 05:34:33 |
| Message-ID: | 000501d4b794$5094d140$f1be73c0$@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Peter Eisentraut wrote:
> When you manage the WAL (or perhaps in the future relation files)
> through PMDK, is there still a file system view of it somewhere, for
> browsing, debugging, and for monitoring tools?
First, I assume that our patchset is used with a filesystem that supports
direct access (DAX) feature, and I test it with ext4 on Linux. You can cd
into pg_wal directory created by initdb -X pg_wal on such a filesystem, and
ls WAL segment files managed by PMDK at runtime.
For each PostgreSQL-specific tool, perhaps yes, but I have not tested yet.
At least, pg_waldump looks working as before.
Regards,
Takashi
--
Takashi Menjo - NTT Software Innovation Center
<menjo(dot)takashi(at)lab(dot)ntt(dot)co(dot)jp>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-01-29 05:55:47 | Re: Allowing extensions to supply operator-/function-specific info |
| Previous Message | Simon Riggs | 2019-01-29 05:33:03 | Re: Allowing extensions to supply operator-/function-specific info |