Re: [COMMITTERS] pgsql: Make it easy to detach completely from shared memory. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Make it easy to detach completely from shared memory.
Date
Msg-id 31745.1395150702@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Make it easy to detach completely from shared memory.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [COMMITTERS] pgsql: Make it easy to detach completely from shared memory.  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Mar 18, 2014 at 8:41 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> Perhaps we should consider a parameter for PGSharedMemoryDetach() ?

> Yeah, maybe.  It seems like a possible modularity violation, because
> the PGSharedMemory... stuff has heretofore not needed to know anything
> about DSM, and apart from this one function, it still wouldn't.

That was exactly the reason we rejected that design upthread.
PGSharedMemoryDetach is specific to the main shmem segment, and in fact
has multiple OS-dependent implementations.

You could make an argument for inventing some new wrapper function that
calls both PGSharedMemoryDetach and dsm_detach_all, but I don't believe
that the existing flavors of that function should know about DSM.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: pg_basebackup --slot=SLOTNAME -X stream
Next
From: Tom Lane
Date:
Subject: Re: pg_archivecleanup bug