Horton

Re: buffer assertion tripping under repeat pgbench load

Greg Smith <greg@2ndquadrant.com>

View thread View on postgr.es
From: Greg Smith <greg@2ndQuadrant.com>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@2ndquadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-12-24T16:25:46Z
Lists: pgsql-hackers 
On 12/24/12 11:10 AM, Simon Riggs wrote:

> I wonder if you're having a hardware problem?

Always possible.  I didn't report this until I had replicated the crash 
and seen exactly the same thing twice.  I've seen it crash on this 
assertion 6 times now.  Bad hardware is not normally so consistent.

I do have another system that's almost identical to this one, except for 
the hard drives.  If progress on tracking down the problem stalls I can 
try to duplicate this on there.

I kicked off another test that includes the block number just before Tom 
suggested it, so I should have the block by tomorrow at the latest.  The 
range of runtime before crash is 3 to 14 hours so far.

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

Commits

  1. Follow TLI of last replayed record, not recovery target TLI, in walsenders.

  2. Avoid holding vmbuffer pin after VACUUM.