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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: Roger Leigh <rleigh(at)whinlatter(dot)ukfsn(dot)org>, 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 21:29:38
Message-ID: 16662.1185658178@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> Roger Leigh wrote:
>> PostgreSQL is using the old SYSV shared memory and semaphores, as evidenced
>> by ipcs:

> 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.

More strongly: it never will be accepted because the POSIX API doesn't
offer the features we need.

You can use POSIX semaphores if you choose (there are compile options
for that), but experience to date says that that degrades performance.
POSIX shared memory is simply not happening.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michał Niklas 2007-07-30 06:10:23 Re: BUG #3493: Cannot find data with = operator
Previous Message Heikki Linnakangas 2007-07-28 17:40:22 Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents