VACUUM causes violent postmaster death - Mailing list pgsql-hackers

From Dan Moschuk
Subject VACUUM causes violent postmaster death
Date
Msg-id 20001103175751.E7597@spirit.jaded.net
Whole thread Raw
Responses Re: VACUUM causes violent postmaster death  (Alfred Perlstein <bright@wintelcom.net>)
Re: VACUUM causes violent postmaster death  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Server process (pid 13361) exited with status 26 at Fri Nov  3 17:49:44 2000
Terminating any active server processes...
NOTICE:  Message from PostgreSQL backend:       The Postmaster has informed me that some other backend died abnormally
andpossibly corrupted shared memory.       I have rolled back the current transaction and am going to terminate your
databasesystem connection and exit.       Please reconnect to the database system and repeat your query.
 

This happens fairly regularly.  I assume exit code 26 is used to dictate
that a specific error has occured.

The database is a decent size (~3M records) with about 4 indexes.

-Dan
-- 
Man is a rational animal who always loses his temper when he is called
upon to act in accordance with the dictates of reason.               -- Oscar Wilde


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Transaction ID wraparound: problem and proposed solution
Next
From: Tom Lane
Date:
Subject: Re: tables permissions once again