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

From Robert Hentosh
Subject Re: Bug #807: Sequence currupted on recovery after kill -9
Date
Msg-id Pine.LNX.4.44.0210291115220.10093-100000@eris.io.com
Whole thread Raw
In response to Bug #807: Sequence currupted on recovery after kill -9  (pgsql-bugs@postgresql.org)
Responses Re: Bug #807: Sequence currupted on recovery after kill -9  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-bugs
On Tue, 29 Oct 2002 pgsql-bugs@postgresql.org wrote:

> Matt Thompson (mthomp@tierfleet.com) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> 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. 
>


The purpose of a sequence is not to insure that the numbers are
consecutive, only to insure that they are unique. If you have failed
inserts, you will see holes also.

I don't know off the top of my head how to do consecutive numbers.  Maybe
only with a table lock.

- robert

pgsql-bugs by date:

Previous
From: Darcy Buskermolen
Date:
Subject: Re: Bug #807: Sequence currupted on recovery after kill -9
Next
From: Tom Lane
Date:
Subject: Re: Bug #807: Sequence currupted on recovery after kill -9