Thread: BUG #6303: ROW_NUMBER()

BUG #6303: ROW_NUMBER()

From
"Alessandro Bellanda"
Date:
The following bug has been logged online:

Bug reference:      6303
Logged by:          Alessandro Bellanda
Email address:      a.bellanda@gmail.com
PostgreSQL version: 9.1.1
Operating system:   Linux CentOS release 5.5 64 bit
Description:        ROW_NUMBER()
Details:

Case:

ROW_NUMBER() OVER (ORDER BY CASE(SUM(expr1)>SUM(expr2),var1,var2))

Error description:
could not find pathkey item to sort

Re: BUG #6303: ROW_NUMBER()

From
bricklen
Date:
On Mon, Nov 21, 2011 at 8:40 AM, Alessandro Bellanda
<a.bellanda@gmail.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =C2=A0 =C2=A0 =C2=A06303
> Logged by: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Alessandro Bellanda
> Email address: =C2=A0 =C2=A0 =C2=A0a.bellanda@gmail.com
> PostgreSQL version: 9.1.1
> Operating system: =C2=A0 Linux CentOS release 5.5 64 bit
> Description: =C2=A0 =C2=A0 =C2=A0 =C2=A0ROW_NUMBER()
> Details:
>
> Case:
>
> ROW_NUMBER() OVER (ORDER BY CASE(SUM(expr1)>SUM(expr2),var1,var2))
>
> Error description:
> could not find pathkey item to sort

Tom Lane has already fixed this. See
http://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dcommitdiff;h=3D167=
9e9feddc94bd7372a6829db92868e55ef7177

Re: BUG #6303: ROW_NUMBER()

From
Andrea Suisani
Date:
On 11/21/2011 06:42 PM, bricklen wrote:
> On Mon, Nov 21, 2011 at 8:40 AM, Alessandro Bellanda
> <a.bellanda@gmail.com>  wrote:
>>
>> The following bug has been logged online:
>>
>> Bug reference:      6303
>> Logged by:          Alessandro Bellanda
>> Email address:      a.bellanda@gmail.com
>> PostgreSQL version: 9.1.1
>> Operating system:   Linux CentOS release 5.5 64 bit
>> Description:        ROW_NUMBER()
>> Details:
>>
>> Case:
>>
>> ROW_NUMBER() OVER (ORDER BY CASE(SUM(expr1)>SUM(expr2),var1,var2))
>>
>> Error description:
>> could not find pathkey item to sort
>
> Tom Lane has already fixed this. See
> http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=1679e9feddc94bd7372a6829db92868e55ef7177
>

and the fix will be included into postgres 9.1.2
(that should be announced on Monday Dec 5, with
  tarballs available from Thursday Dec 1)

Andrea