Re: buffer assertion tripping under repeat pgbench load - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: buffer assertion tripping under repeat pgbench load
Date
Msg-id CA+U5nMJXB0GvPhuOy1DG92NPNUNQmPNroDVWpC1c2C8ofHxtAg@mail.gmail.com
Whole thread Raw
In response to Re: buffer assertion tripping under repeat pgbench load  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 24 December 2012 16:07, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Huh.  Looks a bit like overflow of the refcount, which would explain why
> it takes such a long test case to reproduce it.  But how could that be
> happening without somebody forgetting to decrement the refcount, which
> ought to lead to a visible failure in shorter tests?  Even more
> interesting that the buffer's global refcount is zero.

But we test at the end of each transaction whether any pin count is
non-zero, so it can't have slowly built up.

It would be easier for it to have decremented too many times within
just one transaction.

Something to do with tail recursion during VACUUM?

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: buffer assertion tripping under repeat pgbench load
Next
From: Greg Smith
Date:
Subject: Re: buffer assertion tripping under repeat pgbench load