Skip site navigation (1) Skip section navigation (2)

Re: Bug #807: Sequence currupted on recovery after kill -9

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: mthomp(at)tierfleet(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #807: Sequence currupted on recovery after kill -9
Date: 2002-10-29 17:49:34
Message-ID: 22485.1035913774@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
pgsql-bugs(at)postgresql(dot)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, the sequence will have a corrupted next_value field.  In the example, the value of last_value is 4 before the kill -9 and 34 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

In response to

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2002-10-29 18:54:22
Subject: Re: Bug #807: Sequence currupted on recovery after kill -9
Previous:From: Robert HentoshDate: 2002-10-29 17:18:23
Subject: Re: Bug #807: Sequence currupted on recovery after kill -9

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group