Re: BUG #7600: Database crash with data corruption
Re: BUG #7600: Database crash with data corruption
От:
Michał Hankiewicz <hankiewicz@gmail.com>
Дата:
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
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: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.5) after recovery was completed we have discovered that sequences on
production database had wrong values
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
Re: BUG #7600: Database crash with data corruption
От:
Michał Hankiewicz <hankiewicz@gmail.com>
Дата:
On Mon, Oct 15, 2012 at 3:31 PM, Craig Ringer <ringerc@ringerc.id.au> wrote:
OK, that sounds more like a problem. It wasn't clear from your original post that it was replaying used sequence values.
SIGINT should normally just terminate the statement, eg:
regress=# SELECT pg_sleep(100);
ERROR: canceling statement due to user request
so I agree that something isn't right here.
Is this something you've been able to reproduce? Or is it a one-off incident so far?
--
Craig Ringer
It is just one-off incident. We have increased sequences values and since friday everything is running fine.
We haven't tried to reproduce this situation.
Michał Hankiewicz
