Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
Date
Msg-id 46AB7F86.5080304@enterprisedb.com
Whole thread Raw
In response to BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents  ("Roger Leigh" <rleigh@whinlatter.ukfsn.org>)
Responses Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
List pgsql-bugs
Roger Leigh wrote:
> The following bug has been logged online:

Not a bug, but a feature request...

> PostgreSQL is using the old SYSV shared memory and semaphores, as evidenced
> by ipcs:
> ...
> However, the SYSV memory limit is set in-kernel and while it can be easily
> changed, it is rather less flexible than POSIX SHM support:
> ...
> Having the option of utilising either form of shared memory would be rather
> useful.

A patch to do that submitted was submitted in Spring, but it was not
accepted for 8.3 because there was some issues with it. Search the
archives for more details.

--
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: "Roger Leigh"
Date:
Subject: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
Next
From: Tom Lane
Date:
Subject: Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents