Re: Issues with generate_series using integer boundaries - Mailing list pgsql-general

From Thom Brown
Subject Re: Issues with generate_series using integer boundaries
Date
Msg-id AANLkTikLXHwrY9vx7q0HJNrK9PZR9tNyNRhubOG0Bc8G@mail.gmail.com
Whole thread Raw
In response to Re: Issues with generate_series using integer boundaries  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Issues with generate_series using integer boundaries  (Thom Brown <thom@linux.com>)
List pgsql-general
On 1 February 2011 01:05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thom Brown <thom@linux.com> writes:
>> I've noticed that if I try to use generate_series to include the upper
>> boundary of int4, it never returns:
>
> I'll bet it's testing "currval > bound" without considering the
> possibility that incrementing currval caused an overflow wraparound.
> We fixed a similar problem years ago in plpgsql FOR-loops...

And here's another case:

SELECT x FROM generate_series(2147483643, 2147483644,5) AS a(x);

A step of 1 would work fine, but forcing it to exceed the boundary in
this way means it never returns.

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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Issues with generate_series using integer boundaries
Next
From: Scott Marlowe
Date:
Subject: Re: Why does my DB size differ between Production and DR? (Postgres 8.4)