diff options
author | Bruce Momjian | 2007-11-15 21:14:46 +0000 |
---|---|---|
committer | Bruce Momjian | 2007-11-15 21:14:46 +0000 |
commit | fdf5a5efb7b28c13085fe7313658de8d7b9914f6 (patch) | |
tree | a75cf1422fa1eef4e801cf502b148d8ce1b5dfe7 /src/include/port/linux.h | |
parent | 3adc760fb92eab1a8720337a8bf9b66486609eb3 (diff) |
pgindent run for 8.3.
Diffstat (limited to 'src/include/port/linux.h')
-rw-r--r-- | src/include/port/linux.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/include/port/linux.h b/src/include/port/linux.h index c0dab3ea21b..0f4432a4eff 100644 --- a/src/include/port/linux.h +++ b/src/include/port/linux.h @@ -1,10 +1,10 @@ -/* $PostgreSQL: pgsql/src/include/port/linux.h,v 1.43 2007/07/02 20:11:55 tgl Exp $ */ +/* $PostgreSQL: pgsql/src/include/port/linux.h,v 1.44 2007/11/15 21:14:44 momjian Exp $ */ /* * As of July 2007, all known versions of the Linux kernel will sometimes * return EIDRM for a shmctl() operation when EINVAL is correct (it happens * when the low-order 15 bits of the supplied shm ID match the slot number - * assigned to a newer shmem segment). We deal with this by assuming that + * assigned to a newer shmem segment). We deal with this by assuming that * EIDRM means EINVAL in PGSharedMemoryIsInUse(). This is reasonably safe * since in fact Linux has no excuse for ever returning EIDRM; it doesn't * track removed segments in a way that would allow distinguishing them from |