Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #7600: Database crash with data corruption - Mailing list pgsql-bugs

From Michał Hankiewicz
Subject Re: BUG #7600: Database crash with data corruption
Date
Msg-id CAMpaLZp+ALrSyt27vtJuvW9wOc4u4TZU30Kp78gV4avo3w_DzA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #7600: Database crash with data corruption  (Craig Ringer <ringerc@ringerc.id.au>)
List pgsql-bugs
Tree view
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 <ringerc@ringerc.id.au> wrote:
On 10/12/2012 09:35 PM, hankiewicz@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

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: BUG #7534: walreceiver takes long time to detect n/w breakdown
Next
From: Michał Hankiewicz
Date:
Subject: Re: BUG #7600: Database crash with data corruption