| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ulf Mehlig <ulf(dot)mehlig(at)zmt(dot)uni-bremen(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: NOTICE-message |
| Date: | 2000-10-19 20:40:40 |
| Message-ID: | 11484.971988040@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ulf Mehlig <umehlig(at)uni-bremen(dot)de> writes:
> NOTICE: PortalHeapMemoryFree: 0x0x40b139c8 not in alloc set!
> NOTICE: PortalHeapMemoryFree: 0x0x40b139c8 not in alloc set!
>
> select s_id,nummer,
> min(timest::time) as timest,
^^^^^^^^^^^^^^^^^
> round(avg(photo),2),round(stddev(photo),3),
It turns out that the problem is in the above min() function: min() and
max() are broken in 7.0.* for types time and timetz. The bug is also
causing most of the other aggregate results in the query to be garbage,
BTW.
There is no such bug in current sources because memory management for
aggregates is now done in a cleaner fashion. I'll see about making a
quick-hack patch for 7.0.3, though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Diehl, Jeffrey | 2000-10-19 20:43:12 | RE: MySQL -> pgsql |
| Previous Message | Neil Conway | 2000-10-19 20:34:47 | Re: Any risk in increasing BLCKSZ to get larger tuples? |