BUG #14442: serial maxvalue incorrect

josipa.milic@gmail.com writes:

When table is generated using pgadmin, sequence generated as serial has the
same maxvalue as bigserial: 9223372036854775807

Yup.

It should be max value that corresponds to integer: 2147483647

No, that's intentional. If you never run out of serial numbers,
it's not going to matter. If you do run out, you'll get an error
anyway (from trying to stuff a value > 2147483647 into an integer
column). And the sequence limit will be one less thing you'll
have to change on the way to fixing it.

regards, tom lane

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

On 11/30/16 4:34 AM, josipa.milic@gmail.com wrote:

When table is generated using pgadmin, sequence generated as serial has the
same maxvalue as bigserial: 9223372036854775807

It should be max value that corresponds to integer: 2147483647

There is a pending proposal to address that:
/messages/by-id/898deb94-5265-37cf-f199-4f79ef864536@2ndquadrant.com

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs