Let's remove DSM_IMPL_NONE.

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: michael(at)paquier(dot)xyz, tgl(at)sss(dot)pgh(dot)pa(dot)us, andres(at)anarazel(dot)de, robertmhaas(at)gmail(dot)com
Subject: Let's remove DSM_IMPL_NONE.
Date: 2018-06-26 07:10:26
Message-ID: 20180626.161026.165939767.horiguchi.kyotaro@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


# Subject is fixed.

I think this kind of thing is sutable for doing at the beginning
of a dev cycle.

Since it has been a long time since DSM was introduced and it is
turned on by default and I believe no one turns it off on
purpose. I'd like to propose to get rid of the choice of none.

The motive of this is there's a case where fallback path is
large(?) but scarcely expected to be used.


Kyotaro Horiguchi
NTT Open Source Software Center

Attachment Content-Type Size
v3-0001-Remove-dynamic_shared_memroy_type-none.patch text/x-patch 8.7 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-06-26 07:13:05 Non-reserved replication slots and slot advancing
Previous Message Ideriha, Takeshi 2018-06-26 06:48:28 Global shared meta cache