Re: BUG #6139: LIMIT doesn't return correct result when the value is huge - Mailing list pgsql-bugs

From Alex Hunsaker
Subject Re: BUG #6139: LIMIT doesn't return correct result when the value is huge
Date
Msg-id CAFaPBrReNVPn7EeZ2yonFuGiC6CU1mC6Et0Pnz7hCQNcw7V0dA@mail.gmail.com
Whole thread Raw
In response to BUG #6139: LIMIT doesn't return correct result when the value is huge  ("Hitoshi Harada" <umi.tanuki@gmail.com>)
List pgsql-bugs
On Tue, Aug 2, 2011 at 00:25, Hitoshi Harada <umi.tanuki@gmail.com> wrote:

> db1=3D# select * from test_xy order by x LIMIT 9223372036854775807 OFFSET=
 6;
[ ...]

> db1=3D# select * from test_xy order by x LIMIT pow(2, 63);
> ERROR: =C2=A0bigint out of range
> ERROR: =C2=A0bigint out of range
>
> Maybe a parser converts literal unexpectedly?

pow(2, 63) !=3D 9223372036854775807, pow(2, 63) - 1 does :-). On top of
that pow(2, 63) seems to default to the double variant of pow() which
causes rounding issues. You probably want LIMIT pow(2, 63::numeric)-1.

pgsql-bugs by date:

Previous
From: "Hitoshi Harada"
Date:
Subject: BUG #6139: LIMIT doesn't return correct result when the value is huge
Next
From: Heikki Linnakangas
Date:
Subject: Re: BUG #6139: LIMIT doesn't return correct result when the value is huge