Re: Bug #807: Sequence currupted on recovery after kill -9
От | Robert Hentosh |
---|---|
Тема | Re: Bug #807: Sequence currupted on recovery after kill -9 |
Дата | |
Msg-id | Pine.LNX.4.44.0210291115220.10093-100000@eris.io.com обсуждение исходный текст |
Ответ на | Bug #807: Sequence currupted on recovery after kill -9 (pgsql-bugs@postgresql.org) |
Ответы |
Re: Bug #807: Sequence currupted on recovery after kill -9
|
Список | 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 по дате отправления: