Not sequencial sequence with postgresql

greenhorn · **Posted:** Wed Mar 29, 2006 5:57 am

Hibernate version 2.1

Database we are using is PostgreSQL 8.0.1

We had our server restarted yesterday (we don't know yet how that restart occured, maybe power failure...?) and the first order placed after the reboot had a +32 offset on the sequence...
Could it be that hibernate request a "pool" of id from a sequence and doesn't do a select on each insert as stated in the documentation?
Thanks,
Alex

kgignatyev · **Posted:** Wed Mar 29, 2006 12:58 pm

Could it be that your sequences in the DB were created with CACHE 32 parameter?

http://www.postgresql.org/docs/8.1/stat ... uence.html

greenhorn · **Posted:** Fri Mar 31, 2006 3:49 pm

Well it was not... initially at least. Since the whole database has been moved to newer version since.
I've looked up though, and it is still not.

Code:

SELECT * FROM orders_id_seq;
 sequence_name | last_value | increment_by |      max_value      | min_value | cache_value | log_cnt | is_cycled | is_called 
---------------+------------+--------------+---------------------+-----------+-------------+---------+-----------+-----------
 orders_id_seq |      33634 |            1 | 9223372036854775807 |         1 |           1 |      32 | f         | t     

I couldn't find anything about the log_cnt column though... Has to do with WAL log, but I admit not to know more...