On 18 March 2014 11:59, Robert Haas rh...@postgresql.org wrote:
Make it easy to detach completely from shared memory.
The new function dsm_detach_all() can be used either by postmaster
children that don't wish to take any risk of accidentally corrupting
shared memory; or by forked children of
On Tue, Mar 18, 2014 at 8:41 AM, Simon Riggs si...@2ndquadrant.com wrote:
On 18 March 2014 11:59, Robert Haas rh...@postgresql.org wrote:
Make it easy to detach completely from shared memory.
The new function dsm_detach_all() can be used either by postmaster
children that don't wish to take
Robert Haas robertmh...@gmail.com writes:
On Tue, Mar 18, 2014 at 8:41 AM, Simon Riggs si...@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
On 18 March 2014 13:51, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Tue, Mar 18, 2014 at 8:41 AM, Simon Riggs si...@2ndquadrant.com wrote:
Perhaps we should consider a parameter for PGSharedMemoryDetach() ?
Yeah, maybe. It seems like a possible modularity
