Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA64794 for ; Tue, 10 Aug 1999 10:56:42 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA05143; Tue, 10 Aug 1999 10:55:32 -0400 (EDT) To: Paul Mamin cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Postres falls down on "having" In-reply-to: Your message of Tue, 10 Aug 1999 11:35:11 +0600 <13482.990810@sky.ru> Date: Tue, 10 Aug 1999 10:55:32 -0400 Message-ID: <5141.934296932@sss.pgh.pa.us> From: Tom Lane Paul Mamin writes: > And when result is not empty - everything's Ok. > But when it's empty then [ backend crashes ] I can reproduce this bug with the current development sources. Will look into it. A quick look at a backtrace suggests that the problem is triggered by the "sum(int8(inb))>=maxinb" part of the HAVING clause. You might be able to work around it if you can use int4 or float instead of int8 ... regards, tom lane