| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-10-29 18:54:22 | Re: Bug #807: Sequence currupted on recovery after kill -9 |
| Previous Message | Robert Hentosh | 2002-10-29 17:18:23 | Re: Bug #807: Sequence currupted on recovery after kill -9 |