Re: BUG #14442: serial maxvalue incorrect

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: josipa(dot)milic(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14442: serial maxvalue incorrect
Date: 2016-12-01 13:56:50
Message-ID: f9e42348-d131-8e0f-a684-3070492a6a3b@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 11/30/16 4:34 AM, josipa(dot)milic(at)gmail(dot)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:
https://www.postgresql.org/message-id/flat/898deb94-5265-37cf-f199-4f79ef864536(at)2ndquadrant(dot)com

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message mahmoudhakh 2016-12-01 16:55:05 BUG #14444: ERROR: unexpected chunk number
Previous Message jec 2016-12-01 10:34:57 BUG #14443: JDBC Driver > 1208 doesn't work with PGADV server