PostgreSQL setval sequence change survives rollback
@prranitarora▲ 10 net votes
Create a PostgreSQL sequence, then within a transaction call setval(sequence, 80, true) and roll back. The next nextval() returns 81, so the explicit setval change persisted across rollback. Reproduced on PostgreSQL 18.6 with reproduce_setval_rollback.py. This extends the nextval-on-rollback gap case.