RE: [PoC] Non-volatile WAL buffer - Mailing list pgsql-hackers

From Takashi Menjo
Subject RE: [PoC] Non-volatile WAL buffer
Date
Msg-id 000001d5dff4$995ed180$cc1c7480$@hco.ntt.co.jp_1
Whole thread Raw
In response to Re: [PoC] Non-volatile WAL buffer  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Dear hackers,

I made another WIP patchset to mmap WAL segments as WAL buffers.  Note that this is not a non-volatile WAL buffer
patchsetbut its competitor.  I am measuring and analyzing the performance of this patchset to compare with my N.V.WAL
buffer.

Please wait for a several more days for the result report...

Best regards,
Takashi

--
Takashi Menjo <takashi.menjou.vg@hco.ntt.co.jp>
NTT Software Innovation Center

> -----Original Message-----
> From: Robert Haas <robertmhaas@gmail.com>
> Sent: Wednesday, January 29, 2020 6:00 AM
> To: Takashi Menjo <takashi.menjou.vg@hco.ntt.co.jp>
> Cc: Heikki Linnakangas <hlinnaka@iki.fi>; pgsql-hackers@postgresql.org
> Subject: Re: [PoC] Non-volatile WAL buffer
>
> On Tue, Jan 28, 2020 at 3:28 AM Takashi Menjo <takashi.menjou.vg@hco.ntt.co.jp> wrote:
> > I think our concerns are roughly classified into two:
> >
> >  (1) Performance
> >  (2) Consistency
> >
> > And your "different concern" is rather into (2), I think.
>
> Actually, I think it was mostly a performance concern (writes triggering lots of reading) but there might be a
> consistency issue as well.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company

Attachment

pgsql-hackers by date:

Previous
From: Floris Van Nee
Date:
Subject: RE: Delaying/avoiding BTreeTupleGetNAtts() call within _bt_compare()
Next
From: Dilip Kumar
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions