| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Steve Atkins <steve(at)blighty(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: serial increments on failed insert |
| Date: | 2005-01-15 09:33:07 |
| Message-ID: | 20050115093307.GC27243@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jan 14, 2005 at 17:49:42 -0800,
Steve Atkins <steve(at)blighty(dot)com> wrote:
>
> That's correct, documented behaviour. A serial column is mostly just a
> sequence in disguise. A sequence is guaranteed to give unique,
> increasing values, but in many cases may miss a value (for several
> reasons - in this case because once a sequence value is used, it's
> used, even if the transaction it was used in is rolled back).
Note that the increasing part is only guarenteed within a session,
not accross sessions and only if you haven't changed the sequence
to allow it to roll over.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | lothar.behrens | 2005-01-15 10:00:30 | Re: pgsqlODBC problems |
| Previous Message | Bruno Wolff III | 2005-01-15 09:13:13 | Re: to_char(interval, text) deprecated in future - how do we get consistent interval output without it? |