Re: PG 7.0.3 & RH 7 IPC problems?
| От | DHSC Webmaster |
|---|---|
| Тема | Re: PG 7.0.3 & RH 7 IPC problems? |
| Дата | |
| Msg-id | 3AC37E5E.D729E5BF@dhs-club.com обсуждение исходный текст |
| Ответ на | PG 7.0.3 & RH 7 IPC problems? (DHSC Webmaster <webmaster@dhs-club.com>) |
| Ответы |
Re: PG 7.0.3 & RH 7 IPC problems?
Re: PG 7.0.3 & RH 7 IPC problems? |
| Список | pgsql-admin |
Thank you Tom. Here are the results. [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. Since I am unfamiliar with this output I hesitate to use icprm to remove something which ought not be removed. I have not used kill -9 on anything. :) Tom Lane wrote: > > DHSC Webmaster <webmaster@dhs-club.com> writes: > > It would appear that either my icps is not working or that everything is > > alright. > > Try it as root. I think on Linux, ipcs won't show shm segments that you > do not have read access to (a mighty braindead way to do it but...) > > regards, tom lane -- Bill MacArthur Webmaster DHS Club
В списке pgsql-admin по дате отправления: