Skip site navigation (1) Skip section navigation (2)

VACUUM causes violent postmaster death

From: Dan Moschuk <dan(at)freebsd(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: VACUUM causes violent postmaster death
Date: 2000-11-03 22:57:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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 and possibly corrupted shared memory.
        I have rolled back the current transaction and am going to terminate your database system 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.

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

Next:From: Alfred PerlsteinDate: 2000-11-03 23:03:15
Subject: Re: VACUUM causes violent postmaster death
Previous:From: Tom LaneDate: 2000-11-03 22:56:13
Subject: Re: tables permissions once again

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group