Postgres sequences can skip 32 unexpectedly

Re:Postgres sequences can skip 32 unexpectedly by eyelidlessness on Friday July 16, 2021 @02:50PM (#27859785)

This is a technique used in other ways too. For instance, when opening a new checking account, it’s common to start with an arbitrary number for the first check. And often new businesses will start with an arbitrary invoice number.

[ Parent | on HN ]

Re:Postgres sequences can skip 32 unexpectedly by jdofaz on Friday July 16, 2021 @05:29PM (#27861454)

It used to be common for businesses to refuse to take a check if it had a low check number, the assumption was the account was new and had a higher chance of bouncing. Eventually the banks let you pick or set high numbers so you wouldn't have to deal with that inconvenience.

[ Parent | on HN ]

Re:Postgres sequences can skip 32 unexpectedly by tyingq on Friday July 16, 2021 @04:09PM (#27860676)

There's a fair number of ecommerce setups that default to numerically ascending order numbers also.

[ Parent | on HN ]