Re: Let's remove DSM_IMPL_NONE.

From: Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>
To: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: michael(at)paquier(dot)xyz, peter(dot)eisentraut(at)2ndquadrant(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us, andres(at)anarazel(dot)de, robertmhaas(at)gmail(dot)com
Subject: Re: Let's remove DSM_IMPL_NONE.
Date: 2018-07-09 09:30:22
Message-ID: 20180709093021.GA9309@zakirov.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On Mon, Jul 09, 2018 at 06:07:24PM +0900, Kyotaro HORIGUCHI wrote:
> The new version v4 is changed in the following points.
> - Don't renumber the DSM_IMPL symbols, just removed _NONE.
> - Rewrote the pointed comment.
> - Revised the commit message removing a mention to an
> already-committed patch.
> - (and rebased)

Just a little note. In parallel.sgml it is still mentioned that
dynamic_shared_memory_type accepts 'none' value:

> <xref linkend="guc-dynamic-shared-memory-type"/> must be set to a
> value other than <literal>none</literal>.

Arthur Zakirov
Postgres Professional:
Russian Postgres Company

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Brahmam Eswar 2018-07-09 09:58:45 How to set array element to null value
Previous Message Kyotaro HORIGUCHI 2018-07-09 09:14:13 Re: Non-reserved replication slots and slot advancing