pgsql: "Pin", rather than "keep", dynamic shared memory mappings and se

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: "Pin", rather than "keep", dynamic shared memory mappings and se
Date: 2014-10-30 15:49:54
Message-ID: E1Xjrz0-0002KE-JH@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

"Pin", rather than "keep", dynamic shared memory mappings and segments.

Nobody seemed concerned about this naming when it originally went in,
but there's a pending patch that implements the opposite of
dsm_keep_mapping, and the term "unkeep" was judged unpalatable.
"unpin" has existing precedent in the PostgreSQL code base, and the
English language, so use this terminology instead.

Per discussion, back-patch to 9.4.

Branch
------
REL9_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/1c49dae165bcee69bf3327d6ae20271d82cdf6bf

Modified Files
--------------
src/backend/storage/ipc/dsm.c | 10 +++++-----
src/backend/storage/ipc/dsm_impl.c | 2 +-
src/include/storage/dsm.h | 4 ++--
src/include/storage/dsm_impl.h | 2 +-
4 files changed, 9 insertions(+), 9 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2014-10-30 17:04:23 pgsql: Test IsInTransactionChain, not IsTransactionBlock, in vac_update
Previous Message Tom Lane 2014-10-30 14:10:13 Re: Re: pgsql: Avoid corrupting tables when ANALYZE inside a transaction is rol