Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f34M31804448 for ; Wed, 4 Apr 2001 18:03:02 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f34M2vw12682; Wed, 4 Apr 2001 18:02:57 -0400 (EDT) To: Cedar Cox cc: pgsql-sql@postgresql.org Subject: Re: max( bool )? In-reply-to: References: Comments: In-reply-to Cedar Cox message dated "Thu, 05 Apr 2001 00:02:16 +0200" Date: Wed, 04 Apr 2001 18:02:57 -0400 Message-ID: <12679.986421777@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/62 X-Sequence-Number: 2401 Cedar Cox writes: > And I get this notice: >> > NOTICE: PortalHeapMemoryFree: 0x0x824a6e8 not in alloc set! > NOTICE: Buffer Leak: [059] (freeNext=54, freePrev=58, relname=tblstsc1, > blockNum=0, flags=0x14, refcount=-4 -1) >> > Ver 7.0.2 (sorry, I meant to include this... I think) Okay, this is a known bug; it's fixed in 7.0.3. I'd advise staying away from that sort of construct (sub-select in the output list of a SELECT DISTINCT) until you update --- in some cases the consequences might be worse than just an annoying NOTICE :-(. regards, tom lane