| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Cedar Cox <cedarc(at)visionforisrael(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: max( bool )? |
| Date: | 2001-04-04 22:02:57 |
| Message-ID: | 12679.986421777@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Cedar Cox <cedarc(at)visionforisrael(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phuong Ma | 2001-04-04 22:12:27 | performance inconsistency |
| Previous Message | Cedar Cox | 2001-04-04 22:02:16 | Re: max( bool )? |