Re: eeeh... buffer leak?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lennert Buytenhek <buytenh(at)gnu(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: eeeh... buffer leak?
Date: 2000-10-16 01:27:53
Message-ID: 6389.971659673@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Lennert Buytenhek <buytenh(at)gnu(dot)org> writes:
> ulsec=# truncate job;
> NOTICE: Buffer Leak: [002] (freeNext=-3, freePrev=-3, relname=job, blockNum=0,
> flags=0xc, refcount=1 -1)
> TRUNCATE

Hmm, that's interesting. It shouldn't be possible for PrivateRefCount
(the last value printed) to become negative. Can you give a sequence
for reproducing this notice from a standing start?

The notice isn't especially worrisome in itself, but to the extent that
it implies some incorrect bookkeeping of buffer refcounts, there could
be a problem lurking somewhere.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2000-10-16 01:41:43 Re: reproducable command sequence to get "mdopen: Couldn't open..."
Previous Message Lennert Buytenhek 2000-10-16 00:55:38 eeeh... buffer leak?