Re: Bug #807: Sequence currupted on recovery after kill -9 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Bug #807: Sequence currupted on recovery after kill -9
Date
Msg-id 22485.1035913774@sss.pgh.pa.us
Whole thread Raw
In response to Bug #807: Sequence currupted on recovery after kill -9  (pgsql-bugs@postgresql.org)
List pgsql-bugs
pgsql-bugs@postgresql.org writes:
> Sequence currupted on recovery after kill -9

> Long Description
> If you create a file with an implied sequence and do a couple of inserts, then do a kill -9, when you start up again,
thesequence will have a corrupted next_value field.  In the example, the value of last_value is 4 before the kill -9
and34 when it comes back up. 

This is not corruption, it is the intended behavior.  Only if the
sequence were to go backwards would we consider it a bug.

(There were some sequence-can-go-backwards bugs awhile ago ... but
since you didn't say what version you are using, it's impossible
to guess whether you need an upgrade.)

            regards, tom lane

pgsql-bugs by date:

Previous
From: Robert Hentosh
Date:
Subject: Re: Bug #807: Sequence currupted on recovery after kill -9
Next
From: Bruce Momjian
Date:
Subject: Re: Bug #807: Sequence currupted on recovery after kill -9