| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: shmctl EIDRM preventing startup |
| Date: | 2007-07-02 11:05:35 |
| Message-ID: | 20070702110535.GC12254@svana.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Jul 01, 2007 at 10:39:01PM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Maybe what is happening is that an entirely unrelated process created a
> > segment with that ID, attached to it, and then it was deleted. I don't
> > know how to check however.
>
> AFAIK, EIDRM should imply that the segment has been IPC_RMID'd but still
> exists because there are still processes attached to it. So the thing
> to look for is processes still attached. Not 100% sure how to do that,
> but I'm sure the info is exposed under /proc somehow...
If it's installed, this:
lsof |grep SYSV
Will list all processes attached to a SHM segemtn on the system. I
think ipcs can do the same. You can grep /proc/*/maps for the same
info.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | cha | 2007-07-02 11:32:31 | importing limited set of rows/tuples |
| Previous Message | Dimitri Fontaine | 2007-07-02 09:48:17 | Re: table disk space usage query? |