Re: After ~Crash Sequence not correct - Mailing list pgsql-bugs

From Tom Lane
Subject Re: After ~Crash Sequence not correct
Date
Msg-id 1606.1008783558@sss.pgh.pa.us
Whole thread Raw
In response to After ~Crash Sequence not correct  ("Henshall, Stuart - WCP" <SHenshall@westcountrypublications.co.uk>)
List pgsql-bugs
I have verified that killing the postmaster after a few nextval's
leaves things in a bad state after restart.

I think I see the problem: in nextval(), the sequence data written to
the WAL log is different from that written to the data page.  Isn't
that bogus?

To WAL:
        seq->last_value = next;
        seq->is_called = true;
        seq->log_cnt = 0;

To disk:
    seq->last_value = last;        /* last fetched number */
    seq->is_called = true;
    seq->log_cnt = log;            /* how much is logged */

(also, "log" has been changed between these two points)

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: After ~Crash Sequence not correct
Next
From: Tom Lane
Date:
Subject: Re: After ~Crash Sequence not correct