You misunderstand me. According to the server logs I have sent in the first message process received signal 2 (it is SIGINT) and according to the documentation this signal should not couse server crash. Wrong values of sequences does not mean hole in generated values, but sequence started to generate the same values once again causing unique constraint violation.
regards Michał Hankiewicz On Sat, Oct 13, 2012 at 1:10 PM, Craig Ringer <ring...@ringerc.id.au> wrote: > On 10/12/2012 09:35 PM, hankiew...@gmail.com wrote: > >> 5) after recovery was completed we have discovered that sequences on >> production database had wrong values >> > > To follow up on Tom's explanation, if you're relying on sequences not > having "holes" then your design is dangerously mistaken. A simple ROLLBACK > throws away any IDs that were obtained from sequences in that transaction. > > If you're saying that the sequence is wrong in that it's LOWER than IDs > present in the table, then that's a problem. > > -- > Craig Ringer >
