Skip site navigation (1) Skip section navigation (2)

Re: why not kill -9 postmaster

From: Ray Stell <stellr(at)cns(dot)vt(dot)edu>
To: Shane Ambler <pgsql(at)007Marketing(dot)com>
Cc: Andreas Seltenreich <andreas+pg(at)gate450(dot)dyndns(dot)org>,pgsql-general(at)postgresql(dot)org
Subject: Re: why not kill -9 postmaster
Date: 2006-10-20 14:07:55
Message-ID: 20061020140755.GA20901@cns.vt.edu (view raw or flat)
Thread:
Lists: pgsql-general
On Fri, Oct 20, 2006 at 10:56:09PM +0930, Shane Ambler wrote:

Someone in the thread mentioned having to clean up shared mem.  I've had
to do this often with oracle:

root# ipcs
------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
0xe97c83ac 5505024    oracle    640        807403520  10
0x0052f649 3538945    postgresql600        10461184   2

------ Semaphore Arrays --------
key        semid      owner      perms      nsems
0xfb5e028c 25690112   oracle    640        154
0x0052f649 17629185   postgresq 600        17
0x0052f64a 17661954   postgresq 600        17
0x0052f64b 17694723   postgresq 600        17
0x0052f64c 17727492   postgresq 600        17
0x0052f64d 17760261   postgresq 600        17
0x0052f64e 17793030   postgresq 600        17
0x0052f64f 17825799   postgresq 600        17

------ Message Queues --------
key        msqid      owner      perms      used-bytes   messages

$ ipcrm shm 2588672
resource(s) deleted

this remove example was not from the above shared mem report.

In response to

pgsql-general by date

Next:From: Ron PetersonDate: 2006-10-20 14:09:50
Subject: Re: c function returning high resolution timestamp
Previous:From: Peter BauerDate: 2006-10-20 13:39:40
Subject: Re: Overload after some minutes, please help!

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group