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

Re: Bad error message

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com>
Cc: Decibel! <decibel(at)decibel(dot)org>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bad error message
Date: 2008-10-01 04:09:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> writes:
> On Wed, Oct 1, 2008 at 3:07 AM, Decibel! <decibel(at)decibel(dot)org> wrote:
>> ERROR:  aggregates not allowed in WHERE clause

> No, the real issue is that you are referencing the outer table's column's
> max() in the inner query (correlated sub-query).

Yeah.  It's not easy to see how the software could guess your real
intentions here.  We could maybe offer a vaguely-worded HINT but I'm
not able to think of wording that would be very helpful.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Paul SchlieDate: 2008-10-01 04:43:57
Subject: Re: Block-level CRC checks
Previous:From: Tom LaneDate: 2008-10-01 03:10:51
Subject: Re: Common Table Expressions (WITH RECURSIVE) patch

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