| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | "kassai1972(at)gmail(dot)com" <kassai1972(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15100: sequence behavior on failed insert to a partitioned table |
| Date: | 2018-03-07 11:42:51 |
| Message-ID: | 428781520422971@web24j.yandex.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
<div>Hello</div><div>This is not bug. Sequences are never rollback by design.</div><div> </div><div>https://www.postgresql.org/docs/current/static/sql-createsequence.html</div><div>> Because <code>nextval</code> and <code>setval</code> calls are never rolled back, sequence objects cannot be used if <span>“<span>gapless</span>”</span> assignment of sequence numbers is needed.</div><div> </div><div>regards, Sergei</div>
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/html | 433 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bossart, Nathan | 2018-03-07 15:32:33 | Re: BUG #14941: Vacuum crashes |
| Previous Message | PG Bug reporting form | 2018-03-07 11:29:30 | BUG #15100: sequence behavior on failed insert to a partitioned table |