Re: eeeh... buffer leak?

On Tue, 17 Oct 2000, Tom Lane wrote:

> PrivateRefCount is local to a particular backend, so the behavior of
> other clients shouldn't matter (in theory anyway ;-)).  It should be
> sufficient to reproduce the sequence executed by your specific session.
> Not that that helps much if you don't remember, but please try.

Sorry, I haven't come around this message anymore :(

Could it have been caused by defective hardware?


> > So.. what am I to do if I ever get this message again?
> 
> Don't panic ... but see if you can reproduce it.

Heh.. just think Douglas Adams?


greetings,
Lennert