I was just told in a completely different subject that someone has problems
with 6.3.2 running wild. 

They use PHP and have many persistant connections. Sometimes the following
messages pop up:

NOTICE:  PortalHeapMemoryFree: 0x81c98e0 not in alloc set!
NOTICE:  PortalHeapMemoryFree: 0x81c98b0 not in alloc set!
NOTICE:  PortalHeapMemoryFree: 0x81c9428 not in alloc set!
NOTICE:  PortalHeapMemoryFree: 0x81c93f8 not in alloc set!
NOTICE:  PortalHeapMemoryFree: 0x81c9140 not in alloc set!
NOTICE:  PortalHeapMemoryFree: 0x81c1620 not in alloc set!
NOTICE:  PortalHeapMemoryFree: 0x81c9620 not in alloc set!
NOTICE:  PortalHeapMemoryFree: 0x81c9550 not in alloc set!
NOTICE:  PortalHeapMemoryFree: 0x81c8de0 not in alloc set!
NOTICE:  PortalHeapMemoryFree: 0x81c8dc0 not in alloc set!
NOTICE:  SIAssignBackendId: discarding tag 2147475715
FATAL 1:  Backend cache invalidation initialization failed
NOTICE:  SIAssignBackendId: discarding tag 2147475715
FATAL 1:  Backend cache invalidation initialization failed
NOTICE:  SIAssignBackendId: discarding tag 2147475715

Without ipcclean there is no way to re-start the postmaster after this.

At some point (not always though) some postgres processes start eating the
com,plete CPU time. The load goes up way too high so that watchdog kicks in,
which is the reason why I heard about this.

Does this ring a bell for anyone?

Michael

-- 
Dr. Michael Meskes, Manager of the Western Branch Office, Datenrevision GmbH
work: Cuxhavener Str. 36, D-21149 Hamburg
home: Th.-Heuss-Str. 61,  D-41812 Erkelenz, Michael.Meskes@usa.net
Go SF49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

Sat, 21 Nov 1998 17:00:33 +0100
Michael Meskes <meskes@usa.net>
Problem with 6.3.2
Michael Meskes <meskes@usa.net> writes:
> I was just told in a completely different subject that someone has problems
> with 6.3.2 running wild. 
> They use PHP and have many persistant connections. Sometimes the following
> messages pop up:
> NOTICE:  PortalHeapMemoryFree: 0x81c98e0 not in alloc set!
> [etc]

I haven't seen this myself, but quite a number of serious backend bugs
were fixed between 6.3.2 and 6.4.  My advice is not to bother trying to
debug this problem unless you can reproduce it after installing 6.4.

			regards, tom lane

Sat, 21 Nov 1998 13:46:06 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] Problem with 6.3.2 