Re: (2^63 - 1)::bigint => out of range? (because of the doubleprecision) - Mailing list pgsql-general

From Adrian Klaver
Subject Re: (2^63 - 1)::bigint => out of range? (because of the doubleprecision)
Date
Msg-id 718d7650-fb14-afce-2b34-334bc5cbbd5b@aklaver.com
Whole thread Raw
In response to (2^63 - 1)::bigint => out of range? (because of the double precision)  (Alexey Dokuchaev <danfe@nsu.ru>)
List pgsql-general
On 06/08/2018 10:23 AM, Alexey Dokuchaev wrote:
> Hi there,
> 

> P.S.  On a tangentally related note, why is "NO CYCLE" is the default
> for sequences?
> 
> [*] Per documentation, "The [SQL] standard's AS <data type> expression
> is not supported."  Another "why is it so?" question, btw. ;-)
> 

I found it. Its in the docs for 9.6-. That is not the case anymore in 10+:

https://www.postgresql.org/docs/10/static/sql-createsequence.html
"data_type

     The optional clause AS data_type specifies the data type of the 
sequence. Valid types are smallint, integer, and bigint. bigint is the 
default. The data type determines the default minimum and maximum values 
of the sequence.
"


-- 
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: (2^63 - 1)::bigint => out of range? (because of the doubleprecision)
Next
From: Jeremy Finzel
Date:
Subject: Re: ERROR: found multixact from before relminmxid