Hi,

I've noticed that if I try to use generate_series to include the upper
boundary of int4, it never returns:

SELECT x FROM generate_series(2147483643::int4, 2147483647::int4) AS a(x);

But the same query with int8 returns instantly:

SELECT x FROM generate_series(2147483643::int8, 2147483647::int8) AS a(x);

However, the int8 version of generate_series has the same problem.
This never returns:

SELECT x FROM generate_series(9223372036854775803::int8,
9223372036854775807::int8) AS a(x);

Another issue happens when using the lower boundaries:

postgres=# SELECT x FROM generate_series(-2147483648::int4,
-2147483644::int4) AS a(x);
ERROR:  integer out of range
postgres=# SELECT x FROM generate_series(-9223372036854775808::int8,
-9223372036854775804::int8) AS a(x);
ERROR:  bigint out of range

I've recreated this on 9.0.1 and 9.1devel on a 64-bit platform.

Bug?

-- 
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

Responses

• Re: Issues with generate_series using integer boundaries at 2011-02-01 00:33:27 from Thom Brown
• Re: Issues with generate_series using integer boundaries at 2011-02-01 01:05:25 from Tom Lane

pgsql-hackers by date

Next:	From: Robert Haas	Date: 2011-02-01 00:16:55
	Subject: Re: Error code for "terminating connection due to conflict with recovery"
Previous:	From: Josh Berkus	Date: 2011-02-01 00:13:42
	Subject: Re: Error code for "terminating connection due to conflict with recovery"

pgsql-general by date

Next:	From: Jeff Ross	Date: 2011-02-01 00:28:16
	Subject: Re: Almost full pg_xlog/
Previous:	From: Tom Lane	Date: 2011-02-01 00:14:01
	Subject: Re: Almost full pg_xlog/