DHSC Webmaster <webmaster@dhs-club.com> writes:
> [root@atl01371 linux]# ipcs
> ------ Shared Memory Segments --------
> key shmid owner perms bytes nattch status
> 0x0052e2ca 36864 postgres 700 144 5
> 0x0052e2c1 26625 postgres 600 1104896 5
> 0x0052e2c7 37890 postgres 600 66060 5
> ------ Semaphore Arrays --------
> key semid owner perms nsems status
> 0x0052e2ce 6144 postgres 600 16
> 0x0052e2cf 6145 postgres 600 16
> ------ Message Queues --------
> key msqid owner perms used-bytes messages
> These values don't seem to change from one moment to the next although
> there are of course varying numbers of backends running at any given
> moment.
These objects are created by the postmaster and persist as long as the
postmaster does. They *should* go away when you shut down the
postmaster, but perhaps they didn't for some reason.
Anyway, I suggest (a) shut down postmaster, (b) use ipcs to make sure
there are no postgres shmem or sema objects (delete 'em with ipcrm if
necessary), and (c) try to start postmaster with new -B/-N values.
If step (c) fails when there are no pre-existing objects, then it must
be that you have not managed to increase the kernel's limits on shared
memory. The exact incantations needed to accomplish that trick vary
across systems, so I can't offer a lot of help there.
regards, tom lane
