Re: [7.0.2] problems with spinlock under FreeBSD?
От | Tom Lane |
---|---|
Тема | Re: [7.0.2] problems with spinlock under FreeBSD? |
Дата | |
Msg-id | 26562.967126958@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [7.0.2] problems with spinlock under FreeBSD? (The Hermit Hacker <scrappy@hub.org>) |
Ответы |
Re: [7.0.2] problems with spinlock under FreeBSD?
|
Список | pgsql-hackers |
The Hermit Hacker <scrappy@hub.org> writes: >> What do you get from gdb backtraces on the corefiles? > #2 0x80ee847 in s_lock_stuck (lock=0x20048065 "\001", file=0x816723c "spin.c", line=127) at s_lock.c:51 > #3 0x80ee8c3 in s_lock (lock=0x20048065 "\001", file=0x816723c "spin.c", line=127) at s_lock.c:80 > #4 0x80f1580 in SpinAcquire (lockid=7) at spin.c:127 > #5 0x80f3903 in LockRelease (lockmethod=1, locktag=0xbfbfe674, lockmode=1) at lock.c:1044 > #6 0x80f2af9 in UnlockRelation (relation=0x82063f0, lockmode=1) at lmgr.c:178 > #7 0x806f25e in index_endscan (scan=0x8208780) at indexam.c:284 That's interesting ... someone failing to release lock.c's master spinlock, it looks like. Do you have anything in the postmaster log from just before the crashes? regards, tom lane
В списке pgsql-hackers по дате отправления: