Skip site navigation (1) Skip section navigation (2)

Re: [PORTS] Port Bug Report: Result not "GROUPED BY" from SQL: select im,bn,count(adr) FROM logtmp GROUP BY im,bn;

From: "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su>
To: Arkadiy Vavilin <ar(at)bizlink(dot)ru>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [PORTS] Port Bug Report: Result not "GROUPED BY" from SQL: select im,bn,count(adr) FROM logtmp GROUP BY im,bn;
Date: 1998-01-27 08:40:58
Message-ID: 34CD9D9A.9AB9E39A@sable.krasnoyarsk.su (view raw or flat)
Thread:
Lists: pgsql-hackers
Unprivileged user wrote:
> 
> Category                : runtime: back-end: SQL
> Severity                : critical
> 
> Summary: Result not "GROUPED BY" from SQL: 
> select im,bn,count(adr) FROM logtmp GROUP BY im,bn;

I found from where it comes: nodeGroup.c' funcs assume that slots from
subplan (node Sort) have ttc_shouldFree = FALSE. This was right before
6.2 and is right for in-memory sorts, but wrong for disk ones.
Node Mergejoin uses some tricks to deal with this - #define MarkInnerTuple...
At the moment, I haven't time to fix this bug - will do this latter
if no one else.

Vadim

pgsql-hackers by date

Next:From: Brett McCormickDate: 1998-01-27 08:44:50
Subject: weird query plans involving hash [join] & no indicies
Previous:From: Goran ThyniDate: 1998-01-27 08:39:42
Subject: Re: [HACKERS] postmaster crash and .s.pgsql file

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group