Re: eeeh... buffer leak?

From: Lennert Buytenhek <buytenh(at)gnu(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: eeeh... buffer leak?
Date: 2000-10-25 20:19:08
Message-ID: Pine.LNX.4.21.0010252218070.9513-100000@mara.math.leidenuniv.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Sylvain Simard 2000-10-25 21:02:12 pg_log
Previous Message Sean Kelly 2000-10-25 18:44:30 Re: Updating multiple bool values crashes backend