On 05/01/2017 04:08 PM, Max Wang wrote:
> Hi Adrian,
>
> Only sequences (id) reset to 1.
Then per Amitabh Kant's suggestion take a look at the cycle setting for
the sequences.
For sequence named ts_stamp_test_id_seq:
test=# select * from ts_stamp_test_id_seq ;
-[ RECORD 1 ]-+---------------------
sequence_name | ts_stamp_test_id_seq
last_value | 6
start_value | 1
increment_by | 1
max_value | 9223372036854775807
min_value | 1
cache_value | 1
log_cnt | 0
is_cycled | f
is_called | t
You are looking for whether is_cycled = t
Per the docs:
https://www.postgresql.org/docs/9.6/static/sql-createsequence.html
"CYCLE
NO CYCLE
The CYCLE option allows the sequence to wrap around when the
maxvalue or minvalue has been reached by an ascending or descending
sequence respectively. If the limit is reached, the next number
generated will be the minvalue or maxvalue, respectively.
If NO CYCLE is specified, any calls to nextval after the sequence
has reached its maximum value will return an error. If neither CYCLE or
NO CYCLE are specified, NO CYCLE is the default.
"
>
> Regards,
> Max
>
--
Adrian Klaver
adrian.klaver@aklaver.com
