Re: vacuum info - crash - Mailing list pgsql-admin

From Tom Lane
Subject Re: vacuum info - crash
Date
Msg-id 25683.1053927247@sss.pgh.pa.us
Whole thread Raw
In response to vacuum info - crash  ("Eko Pranoto" <koprapostgres@telkom.net>)
List pgsql-admin
"Eko Pranoto" <koprapostgres@telkom.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

pgsql-admin by date:

Previous
From: "Somasekhar Bangalore"
Date:
Subject: unsubscribe
Next
From: "Eugene M. Zheganin"
Date:
Subject: Re: Full vacuuming of BIG tables takes too long