Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e664iqS91114 for ; Thu, 6 Jul 2000 00:44:52 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id AAA20355; Thu, 6 Jul 2000 00:44:25 -0400 (EDT) To: Paul McGarry cc: pgsql-sql@hub.org Subject: Re: ERROR: ExecEvalAggref: no aggregates in this expressioncontext In-reply-to: <3963DA0C.B248C79D@opentec.com.au> References: <200007042201.e64M1GS36467@hub.org> <3962834C.5EF48AB7@opentec.com.au> <3397.962817322@sss.pgh.pa.us> <3963DA0C.B248C79D@opentec.com.au> Comments: In-reply-to Paul McGarry message dated "Thu, 06 Jul 2000 10:59:57 +1000" Date: Thu, 06 Jul 2000 00:44:24 -0400 Message-ID: <20348.962858664@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200007/54 Paul McGarry writes: >> Yup. ExecEvalAggref is supposed to fetch the result of a (previously >> computed) aggregate function. It's unhappy because it's not finding >> anything to return. This is a bug --- can we see a complete example >> that causes it? > The view that I am experiencing this error on is rather nasty, so > much so that I am going to solve the problem it was supposed to > solve in another way. View? Hmm, we know that views involving GROUP BY or aggregates don't work very well. We hope to fix those problems in 7.2, but right now there's probably not much that can be done about it. I'd recommend avoiding views that use those features for now. regards, tom lane