Spinlock error

Поиск
Список
Период
Сортировка
От Jeff MacDonald
Тема Spinlock error
Дата
Msg-id Pine.BSF.4.10.10001271436530.380-100000@rage.hub.org
обсуждение исходный текст
Ответы Re: [HACKERS] Spinlock error  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Hi folks,

I got a problem with a production database, it's a little
busy with 2 to 5 queries per second. 

Running on Redhat 6.0, 2.2.5-15 SMP (intel)

Currently thre are 128 backends ( postmaster -N 128 )
with share mem set at 256.

in pg_options verbose = 2, syslog = 2,

here are the errors..

FATAL: s_lock(4001404d) at spin.c:125, stuck spinlock. Aborting.

After those spinlock errors the postmaster died.... I tries to start it
back up and it failed with this error.

FindExec: found "/usr/bin/postgres" using argv[0]
IpcMemoryCreate: shmget failed (Identifier removed) key=5432010,
size=120, permission=700
IpcMemoryIdGet: shmget failed (Identifier removed) key=5432010, size=120,
permission=0
IpcMemoryAttach: shmat failed (Invalid argument) id=-2
FATAL 1:  AttachSLockMemory: could not attach segment
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)


Since this is a production database, what are teh first steps i should
take ?



======================================================
Jeff MacDonaldjeff@pgsql.com    irc: bignose on EFnet
======================================================



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [SQL] DISTINCT ON: speak now or forever hold your peace
Следующее
От: "Ross J. Reedstrom"
Дата:
Сообщение: Re: [HACKERS] Column ADDing issues