Port Bug Report: Unpredictable backend behavior on Solaris 2.7

From: Unprivileged user <nobody>
To: pgsql-ports(at)postgresql(dot)org
Subject: Port Bug Report: Unpredictable backend behavior on Solaris 2.7
Date: 1999-02-09 23:27:05
Message-ID: 199902092327.SAA52534@hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-ports


============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : Daryl W. Dunbar
Your email address : daryl(at)www(dot)com

Category : runtime: back-end
Severity : critical

Summary: Unpredictable backend behavior on Solaris 2.7

System Configuration
--------------------
Operating System : Solaris 2.7

PostgreSQL version : 6.4.2

Compiler used : gcc 2.8.1

Hardware:
---------
Sparc 20

Versions of other tools:
------------------------
gmake, flex

--------------------------------------------------------------------------

Problem Description:
--------------------
Occasionally, the backend does one of the following:
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend died abnormally a
nd possibly corrupted shared memory.
I have rolled back the current transaction and am going to terminate you
r database system connection and exit.
Please reconnect to the database system and repeat your query.

or
NOTICE: Deadlock detected -- See the lock(l) manual page for a possible cause.
ERROR: WaitOnLock: error on wakeup - Aborting this transaction

or
IpcSemaphoreCreate: semget failed (No space left on device) key=5432815, num=16,
permission=600
{the drives are nearly empty!}

and lots and lots of
FATAL: pq_putnchar: fputc() failed: errno=32

--------------------------------------------------------------------------

Test Case:
----------
Are there some tips for compiling under Solaris 2.7??

Your assistance is greatly appreciated!

--------------------------------------------------------------------------

Solution:
---------

--------------------------------------------------------------------------

Browse pgsql-ports by date

  From Date Subject
Next Message John Gotts 1999-02-10 19:03:00 LOAD Regression Failures with BSDI 3.1
Previous Message Mary Pat Reeve 1999-02-09 16:17:57 Alpha 4.0d SLOCK problems v6.4.2