Re: buffer assertion tripping under repeat pgbench load
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Smith <greg@2ndQuadrant.com>
Cc: Simon Riggs <simon@2ndQuadrant.com>, Andres Freund <andres@2ndQuadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-12-24T16:56:44Z
Lists: pgsql-hackers
Greg Smith <greg@2ndQuadrant.com> writes: > 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. Cool. Once you get the crash, please also capture the contents of the index's metapage --- pg_filedump or contrib/pageinspect's bt_metap() should do. If the problem page isn't the metapage itself, we'll need that info to tell if it's the root. Actually, it might be interesting to capture the content of the problem page itself, too, if it isn't the metapage. "pg_filedump -i -F" or contrib/pageinspect's bt_page_stats() + bt_page_items() should show anything useful. regards, tom lane
Commits
-
Follow TLI of last replayed record, not recovery target TLI, in walsenders.
- af275a12dfee 9.3.0 cited
-
Avoid holding vmbuffer pin after VACUUM.
- 62656617dbe4 9.3.0 cited