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

Re: Fw: PortalHeapMemoryFree error in OpenACS

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Brian Mueller" <brian(at)twotomatoes(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Fw: PortalHeapMemoryFree error in OpenACS
Date: 2000-08-19 20:14:36
Message-ID: 29880.966716076@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Brian Mueller" <brian(at)twotomatoes(dot)com> writes:
> When doing a large query from either an OpenACS 3.2.2 web page (/intranet/e=
> mployees/admin/index.tcl) or from psql, I get the following error:
> NOTICE:  PortalHeapMemoryFree: 0x0x41a37610 not in alloc set!
> NOTICE:  PortalHeapMemoryFree: 0x0x41a37cc8 not in alloc set!
> NOTICE:  PortalHeapMemoryFree: 0x0x41a37ca0 not in alloc set!
> ERROR:  btree scan list trashed; can't find 0x0x41a37bf0

Brian, it looks like this problem has already been fixed in current CVS
sources --- it's a foulup in subplan handling for APPEND plans, which
basically means that you need sub-SELECTS in a UNION to cause it.

Easiest patch for 7.0.* is to grab src/backend/optimizer/plan/setrefs.c
out of the CVS server or a recent nightly snapshot tarball and drop it
into 7.0.* sources as-is.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2000-08-19 22:17:13
Subject: Re: Alternate data locations ?
Previous:From: Patrick SpinlerDate: 2000-08-19 04:30:44
Subject: Alternate data locations ?

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