pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Takashi Menjo <takashi.menjo@gmail.com>
Cc: pgsql-hackers@postgresql.org, Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Tsunakawa, Takayuki <tsunakawa.takay@fujitsu.com>
Cc: Deng, Gang <gang.deng@intel.com>
Cc: Takashi Menjo <takashi.menjou.vg@hco.ntt.co.jp>
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: Daniel Gustafsson <daniel@yesql.se>
Subject: Re: Map WAL segment files on PMEM as WAL buffers
Date: Wed, 5 Jan 2022 23:19:08 -0600
Message-ID: <20220106051908.GV14051@telsasoft.com> (raw)
In-Reply-To: <CA+hUKGL4CjH5+ZJGwgZapj0ZSPbptCz=kHPDEu-N+JJMRANZtA@mail.gmail.com>
References: <CAOwnP3MoYjRStgyPbYYvKYda=bOGsoCVJALJ63AGyg+=Wf=g9A@mail.gmail.com>
	<CAEze2WgqpS86RqDsQK7fRk1mEJsV+hVQEt7qa-AkdEFsm-XjMQ@mail.gmail.com>
	<CAOwnP3N9p5byYUag4h+_7Z9+vmDgMNVs+Wuu9n2c6JUFk1jibg@mail.gmail.com>
	<CAOwnP3OaRYEgj0xCpXEJ2Pa7-52euL+gOTM8eMa+fOwpUPU4ZA@mail.gmail.com>
	<CEEFC453-353D-40B8-859F-6DF9ADF6F4BE@yesql.se>
	<CAOwnP3O6SWP6GO-o2RfkrDcF+5g3Y+K+L9Hp_6m3KSKebdm6Hg@mail.gmail.com>
	<CAOwnP3PS4fRNCOkGvSf1USv_bHSgQzMzn6CrbpbV1HM8nse1eQ@mail.gmail.com>
	<CAOwnP3N6Zi2nQ0WzuXA69w2mhZ5R5uvVJUDNH92CTA09MErh9g@mail.gmail.com>
	<20220106040000.GU14051@telsasoft.com>
	<CA+hUKGL4CjH5+ZJGwgZapj0ZSPbptCz=kHPDEu-N+JJMRANZtA@mail.gmail.com>

On Thu, Jan 06, 2022 at 05:52:01PM +1300, Thomas Munro wrote:
> On Thu, Jan 6, 2022 at 5:00 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
> > I'm attaching a probable fix.  Unfortunately, for patches like this, most of
> > the functionality isn't exercised unless the library is installed and
> > compilation and runtime are enabled by default.
> 
> By the way, you could add a separate patch marked not-for-commit that
> adds, say, an apt-get command to the Linux task in the .cirrus.yml
> file, and whatever --with-blah stuff you might need to the configure
> part, if that'd be useful to test this code.

In general, I think that's more or less essential.

But in this case it really doesn't work :(

running bootstrap script ... 2022-01-05 23:17:30.244 CST [12088] FATAL:  file not on PMEM: path "pg_wal/000000010000000000000001"

-- 
Justin





view thread (22+ messages)  latest in thread

Message-ID: <20220106051908.GV14051@telsasoft.com>
Permalink:  ../20220106051908.GV14051@telsasoft.com/
Also on:    postgresql.org/message-id/20220106051908.GV14051@telsasoft.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: pryzby@telsasoft.com, thomas.munro@gmail.com, takashi.menjo@gmail.com, tomas.vondra@enterprisedb.com, sawada.mshk@gmail.com, hlinnaka@iki.fi, tsunakawa.takay@fujitsu.com, gang.deng@intel.com, takashi.menjou.vg@hco.ntt.co.jp, boekewurm+postgres@gmail.com, daniel@yesql.se
  Subject: Re: Map WAL segment files on PMEM as WAL buffers
  In-Reply-To: <20220106051908.GV14051@telsasoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox