Hi,
I've seen this (see below) in the postmaster's log-file.
I doubt this is normal behaviour.
I'm using PostgreSQL 7.2.3 on hppa-hp-hpux10.20, compiled by GCC 2.95.2
Does anybody know what may cause calls to semctl resp. shmctl
(semaphore control resp. shared memory control) to fail?
The application program ( C code using the libpq - C Library )
crashed because of a segmentation violation.
I've searched the archive for
ZeroProcSemaphore
IpcSemaphoreKill
IpcMemoryDelete
with no results.
Any hints welcome. Thanks in advance.
Regards, Christoph
DEBUG: database system is ready
NOTICE: COMMIT: no transaction in progress
<cut>
NOTICE: COMMIT: no transaction in progress
DEBUG: pq_recvbuf: unexpected EOF on client connection
DEBUG: pq_recvbuf: unexpected EOF on client connection
ZeroProcSemaphore: semctl(id=2450,SETVAL) failed: Invalid argument
DEBUG: server process (pid 10237) exited with exit code 255
DEBUG: terminating any other active server processes
DEBUG: all server processes terminated; reinitializing shared memory
and semaphores
IpcSemaphoreKill: semctl(707088, 0, IPC_RMID, ...) failed: Invalid
argument
IpcSemaphoreKill: semctl(2449, 0, IPC_RMID, ...) failed: Invalid
argument
IpcSemaphoreKill: semctl(2450, 0, IPC_RMID, ...) failed: Invalid
argument
IpcMemoryDelete: shmctl(312410, 0, 0) failed: Invalid argument
DEBUG: database system was interrupted at 2003-02-17 11:22:36 MET
DEBUG: checkpoint record is at 0/47EA788
DEBUG: redo record is at 0/47EA788; undo record is at 0/0; shutdown
TRUE
DEBUG: next transaction id: 16242; next oid: 368814
DEBUG: database system was not properly shut down; automatic recovery
in progress
DEBUG: redo starts at 0/47EA7C8
DEBUG: ReadRecord: record with zero length at 0/48864B8
DEBUG: redo done at 0/4886490
DEBUG: database system is ready