[Info-ingres] Duplicate sequence values

Roy Hann specially at processed.almost.meat
Fri Sep 13 09:41:31 UTC 2019


We've got a database that is cloned overnight from another system. In
iisequences I see that next_value is (e.g.) 1200. However when I 

  select next value for my_seq;

I get a value like 889, which usually turns out to be a duplicate. 

The cached state of the sequence seems to be retained even though the
database was closed for the cloning operation. 

I know we're fooling about with checkpoints in a not-totally sanctioned
way, but surely when the database is opened by the first user the cached
value should be refreshed? I can call it a bug right?

Roy

PS: It's just a nuisance, not a show-stopper. As a workaround I do

  alter sequence my_seq increment by 1;





More information about the Info-ingres mailing list