Tom Lane
authored
This is a Linux kernel bug that apparently exists in every extant kernel version: sometimes shmctl() will fail with EIDRM when EINVAL is correct. We were assuming that EIDRM indicates a possible conflict with pre-existing backends, and refusing to start the postmaster when this happens. Fortunately, there does not seem to be any case where Linux can legitimately return EIDRM (it doesn't track shmem segments in a way that would allow that), so we can get away with just assuming that EIDRM means EINVAL on this platform. Per reports from Michael Fuhr and Jon Lapham --- it's a bit surprising we have not seen more reports, actually.
| Name | Last commit | Last update |
|---|---|---|
| .. | ||
| aix | ||
| darwin | ||
| dynloader | ||
| hpux | ||
| nextstep | ||
| sunos4 | ||
| tas | ||
| win32 | ||
| Makefile | ||
| ipc_test.c | ||
| posix_sema.c | ||
| sysv_sema.c | ||
| sysv_shmem.c | ||
| win32_sema.c | ||
| win32_shmem.c | ||