| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "anilkumar(dot)gv(at)gmail(dot)com" <anilkumar(dot)gv(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | BUG #15010: Sequence ID is getting skipped |
| Date: | 2018-01-15 07:36:40 |
| Message-ID: | CAKFQuwbn=KdJz=E-=R-VMyVpWuUu6Ak1fwzQxtDxf7=1Fa2ecg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sunday, January 14, 2018, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15010
> Logged by: Anil Kumar G V
> Email address: anilkumar(dot)gv(at)gmail(dot)com
> PostgreSQL version: 9.3.0
> Operating system: Ubuntu
> Description:
>
> Sometime sequence ID is getting skipped by 32 numbers. Here is some sample
> sequence definition.
>
I don't think the exact cause of this particular skipping is documented
(it's database startup, maybe crash, related I think) but sequences are not
promised to be gap-less.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2018-01-15 08:45:37 | Re: BUG #15010: Sequence ID is getting skipped |
| Previous Message | Michael Paquier | 2018-01-15 07:25:37 | Re: BUG #14999: pg_rewind corrupts control file global/pg_control |