Re: vacuum info - crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Eko Pranoto" <koprapostgres(at)telkom(dot)net>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: vacuum info - crash
Date: 2003-05-26 05:34:07
Message-ID: 25683.1053927247@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Eko Pranoto" <koprapostgres(at)telkom(dot)net> writes:
> I have recieve information from vacuum verbose analyze
> I don't know meaning of "Crash 5402"

A little digging in the source code finds that that count last appeared
in 7.1, and it said

/*
* Not Aborted, Not Committed, Not in Progress -
* so it's from crashed process. - vadim 11/26/96
*/
ncrash++;

ie., you had 5402 rows that were inserted by a transaction that crashed
before committing.

My take on it would be that you should consider updating to a newer
Postgres release. Whatever the problem was, it's likely to have been
fixed.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Eugene M. Zheganin 2003-05-26 07:48:51 Re: Full vacuuming of BIG tables takes too long
Previous Message Somasekhar Bangalore 2003-05-26 04:02:19 unsubscribe