2012/8/7 Kevin Grittner <Kevin.Grittner@wicourts.gov>:
> I also think it's a problem that one can get through the entire
> "Concurrency Control" chapter (mvcc.sgml) without a clue that
> sequences aren't transactional.
It is possible to say that they *are* transactional when considering
the following definition: nextval() doesn’t always give you “the” next
value, but “some” next value that is higher than the one gotten by any
preceding transactions.
I personally like it better to introduce this minor complexity in the
definition of sequences, rather than messing with the definition of
transactionality.
Nicolas
--
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?