From 0ac5e5a7e152504c71ce2168acc9cef7fde7893c Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Wed, 9 Oct 2013 21:05:02 -0400 Subject: Allow dynamic allocation of shared memory segments. Patch by myself and Amit Kapila. Design help from Noah Misch. Review by Andres Freund. --- doc/src/sgml/config.sgml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index e8e8e6f8fcd..77a9303933d 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1194,6 +1194,32 @@ include 'filename' + + dynamic_shared_memory_type (enum) + + dynamic_shared_memory_type configuration parameter + + + + Specifies the dynamic shared memory implementation that the server + should use. Possible values are posix (for POSIX shared + memory allocated using shm_open), sysv + (for System V shared memory allocated via shmget), + windows (for Windows shared memory), mmap + (to simulate shared memory using memory-mapped files stored in the + data directory), and none (to disable this feature). + Not all values are supported on all platforms; the first supported + option is the default for that platform. The use of the + mmap option, which is not the default on any platform, + is generally discouraged because the operating system may write + modified pages back to disk repeatedly, increasing system I/O load; + however, it may be useful for debugging, when the + pg_dynshmem directory is stored on a RAM disk, or when + other shared memory facilities are not available. + + + + -- cgit v1.2.3