Dramatically reduce System V shared memory consumption.
Except when compiling with EXEC_BACKEND, we'll now allocate only a tiny
amount of System V shared memory (as an interlock to protect the data
directory) and allocate the rest as anonymous shared memory via mmap.
This will hopefully spare most users the hassle of adjusting operating
system parameters before being able to start PostgreSQL with a
reasonable value for shared_buffers.
There are a bunch of documentation updates needed here, and we might
need to adjust some of the HINT messages related to shared memory as
well. But it's not 100% clear how portable this is, so before we
write the documentation, let's give it a spin on the buildfarm and
see what turns red.
src/backend/port/sysv_shmem.c | 89 +++++++++++++++++++++++++++++++++++++++-
1 files changed, 86 insertions(+), 3 deletions(-)
pgsql-committers by date
|Next:||From: Alvaro Herrera||Date: 2012-06-28 15:58:28|
|Subject: Re: pgsql: Fix install program detection|
|Previous:||From: Robert Haas||Date: 2012-06-28 12:16:04|
|Subject: pgsql: Add missing space in event_source GUC description.|