| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-30 04:37:20 |
| Message-ID: | CA+Tgmob6k=X=mgnoYy9Aq8+jDYUBfH_WaDKqn30DkGkh1FZByA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 29, 2012 at 10:07 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> It is a strange power of two to be appearing there. I can follow your
> reasoning for why this could be a bit flipping error. There's no sign of
> that elsewhere though, no other crashes under load. I'm using this server
> here because it's worked fine for a while now.
In theory, if this is sufficiently reproducible, could you start
backing up through the commit history 100 or so commits at a time
until you find the culprit? Or use git bisect? It'd be kind of
time-consuming, but...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2012-12-30 04:45:02 | Re: buffer assertion tripping under repeat pgbench load |
| Previous Message | Peter Geoghegan | 2012-12-30 04:21:31 | Re: enhanced error fields |