From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Brian Hirt <bhirt(at)mobygames(dot)com> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WARNING: buffer refcount leak |
Date: | 2004-07-26 21:52:03 |
Message-ID: | 10206.1090878723@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Brian Hirt <bhirt(at)mobygames(dot)com> writes:
> I'm working on a new machine, and i think it's got possible bad
> hardware, since that seems more likely than a bug in postgresql. I'm
> wondering if someone has any idea what kind of hardware failure might
> cause this message:
> WARNING: buffer refcount leak: [424] (freeNext=425, freePrev=423,
> rel=0/0, blockNum=4294967295, flags=0x1c, refcount=-631 30464)
My money is on bad RAM. That refcount is ridiculous, and I can't see
any way for a disk problem to cause that. (Unless this shared-buffer
header got swapped out and back in, which seems unlikely considering we
use the shared buffer headers a lot.) Seems like it's got to be bad
RAM, bad CPU, or some part directly between them --- and you already
replaced all those parts.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2004-07-26 22:06:49 | Re: 7.5 backend crash |
Previous Message | Tom Lane | 2004-07-26 21:22:36 | Re: 7.5 backend crash |