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

From Greg Smith
Subject Re: buffer assertion tripping under repeat pgbench load
Date
Msg-id 50DB5209.8020101@2ndQuadrant.com
Whole thread Raw
In response to Re: buffer assertion tripping under repeat pgbench load  ("anarazel@anarazel.de" <andres@anarazel.de>)
List pgsql-hackers
On 12/26/12 1:58 PM, anarazel@anarazel.de wrote:

> I don't think its necessarily only one buffer - if I read the above output correctly Greg used the suggested debug
outputwhich just put the elog(WARN) before the Assert...
 
>
> Greg, could you output all "bad" buffers and only assert after the loop if there was at least one refcounted buffer?

I've been doing that for a while, the only thing that's new is getting 
the block number.  It's only ever been one buffer involved.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: "anarazel@anarazel.de"
Date:
Subject: Re: buffer assertion tripping under repeat pgbench load
Next
From: Josh Berkus
Date:
Subject: Re: Feature Request: pg_replication_master()