Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Roger Leigh <rleigh(at)whinlatter(dot)ukfsn(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
Date: 2007-07-28 17:40:22
Message-ID: 46AB7F86.5080304@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2007-07-28 21:29:38 Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
Previous Message Roger Leigh 2007-07-28 17:09:21 BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents