backend died - Mailing list pgsql-hackers

<p><font size="2">Our customer running Postgres v. 7.3.2 reported a problem, occurring</font><br /><font
size="2">coupletimes a week on three different servers, all on Solaris 9.</font><br /><font size="2">We enabled
debuggingin postgresql.conf, now it happened again;</font><br /><font size="2">here's the excerpt from the database
log:</font><p><fontsize="2">2004-11-13 10:01:06 [10456]  DEBUG:  child process (pid 19285) was terminated by signal
10</font><br/><font size="2">2004-11-13 10:01:06 [10456]  LOG:  server process (pid 19285) was terminated by signal
10</font><br/><font size="2">2004-11-13 10:01:06 [10456]  LOG:  terminating any other active server processes</font><br
/><fontsize="2">2004-11-13 10:01:06 [10456]  DEBUG:  CleanupProc: sending SIGQUIT to process 10876</font><br /><font
size="2">2004-11-1310:01:06 [10456]  DEBUG:  CleanupProc: sending SIGQUIT to process 10482</font><br /><font
size="2">2004-11-1310:01:06 [10456]  DEBUG:  CleanupProc: sending SIGQUIT to process 10481</font><br /><font
size="2">2004-11-1310:01:06 [10456]  DEBUG:  CleanupProc: sending SIGQUIT to process 10478</font><br /><font
size="2">2004-11-1310:01:06 [10456]  DEBUG:  CleanupProc: sending SIGQUIT to process 10472</font><br /><font
size="2">2004-11-1310:01:06 [10876]  WARNING:  Message from PostgreSQL backend:</font><br /><font size="2">        The
Postmasterhas informed me that some other backend</font><br /><font size="2">        died abnormally and possibly
corruptedshared memory.</font><br /><font size="2">        I have rolled back the current transaction and am</font><br
/><fontsize="2">        going to terminate your database system connection and exit.</font><br /><font size="2">       
Pleasereconnect to the database system and repeat your query.</font><br /><font size="2">2004-11-13 10:01:06 [10478] 
WARNING: Message from PostgreSQL backend:</font><br /><font size="2">        The Postmaster has informed me that some
otherbackend</font><br /><font size="2">        died abnormally and possibly corrupted shared memory.</font><br /><font
size="2">       I have rolled back the current transaction and am</font><br /><font size="2">        going to terminate
yourdatabase system connection and exit.</font><br /><font size="2">        Please reconnect to the database system and
repeatyour query.</font><br /><font size="2">2004-11-13 10:01:06 [10482]  WARNING:  Message from PostgreSQL
backend:</font><br/><font size="2">        The Postmaster has informed me that some other backend</font><br /><font
size="2">       ... ...</font><p><font size="2">There's no other references to process 19285 in the log file.</font><br
/><fontsize="2">If it helps the servers are configured to use UDS.</font><br /><font size="2">The socket files are
placedin different directories (each db's PGDATA)</font><p><font size="2">Would it be helful to change the debug level
fromDEBUG1 to a higher value?</font><br /><font size="2">What else should I look at?</font><p><font size="2">Thank
you,</font><br/><font size="2">Mike</font><br />