You mis
understand 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
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