Re: eeeh... buffer leak? - Mailing list pgsql-bugs

From Tom Lane
Subject Re: eeeh... buffer leak?
Date
Msg-id 6389.971659673@sss.pgh.pa.us
Whole thread Raw
In response to eeeh... buffer leak?  (Lennert Buytenhek <buytenh@gnu.org>)
Responses Re: eeeh... buffer leak?
List pgsql-bugs
Lennert Buytenhek <buytenh@gnu.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

pgsql-bugs by date:

Previous
From: Lennert Buytenhek
Date:
Subject: eeeh... buffer leak?
Next
From: Philip Warner
Date:
Subject: Re: reproducable command sequence to get "mdopen: Couldn't open..."