Re: VACUUM causes violent postmaster death

From: Alfred Perlstein <bright(at)wintelcom(dot)net>
To: Dan Moschuk <dan(at)freebsd(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: VACUUM causes violent postmaster death
Date: 2000-11-03 23:03:15
Message-ID: 20001103150315.C5112@fw.wintelcom.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Dan Moschuk <dan(at)freebsd(dot)org> [001103 14:55] wrote:
>
> 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.

What version of postgresql? Tom Lane recently fixed some severe problems
with vacuum and heavily used databases, the fix should be in the latest
7.0.2-patches/7.0.3 release.

--
-Alfred Perlstein - [bright(at)wintelcom(dot)net|alfred(at)freebsd(dot)org]
"I have the heart of a child; I keep it in a jar on my desk."

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-11-03 23:09:43 Re: VACUUM causes violent postmaster death
Previous Message Dan Moschuk 2000-11-03 22:57:51 VACUUM causes violent postmaster death