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: 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: Sat, 28 Jul 2007 17:29:38 -0400
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
- References:
- BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
- From: Roger Leigh
- Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
- From: Heikki Linnakangas
- BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
- Prev by Date: Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
- Next by Date: Re: BUG #3493: Cannot find data with = operator
- Previous by thread: Re: BUG #3495: PostgreSQL does not use POSIX SHM or SEM in place of SYSV equivalents
- Next by thread: Some errors in PostgreSQL installestion
- Indexes: