Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Sat, 28 Jul 2007 18:40:22 +0100
- Message-id: <46AB7F86.5080304@enterprisedb.com> <text/plain>
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
- Follow-Ups:
- References:
- Prev by Date: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
- Next by Date: Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
- Previous by thread: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
- Next by thread: Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
- Indexes: