Re:Postgres sequences can skip 32 unexpectedly
by combatentropy on Thursday July 15, 2021 @06:34PM
(#27850909)
Right. It isn't something I recommend running in production before every insert. It's just something I have done sometimes, like as part of a big database change, and only to "reference" tables. Like suppose there is a table of 10 rows to populate a dropdown menu. Now I need to add an 11th, but for some reason the sequence got out of wack, and the next sequence value is 15. So I manually set it back to 11.
[ Parent
| on HN ]
There are no comments on this comment yet.