From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: buffer assertion tripping under repeat pgbench load |
Date: | 2012-12-26 22:28:09 |
Message-ID: | CAM-w4HNpog0YA+Mm4QeES9JhbK+3GSZfyhHhJtS_C-A66B=Xow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 26, 2012 at 6:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Yeah, that destroys my theory that there's something broken about index
> management specifically. Now we're looking for something that can
> affect any buffer's refcount, which more than likely means it has
> nothing to do with the buffer's contents ...
Hardware problem is still a plausible candidate. Have you run any
memory checker software or seen anything else crash? Classically gcc
is as good at detecting memory problems as memory checking software.
Or a bad cpu can also sometimes cause problems like this. Have you
been able to reproduce on any other machines?
Did you ever say what kind of hardware it was? This is the local
reference count so I can't see how it could be a race condition or
anything like that but it sure smells a bit like one.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2012-12-26 22:40:09 | Re: buffer assertion tripping under repeat pgbench load |
Previous Message | Andrew Dunstan | 2012-12-26 20:33:59 | json api WIP patch |