| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: buffer assertion tripping under repeat pgbench load |
| Date: | 2012-12-23 18:10:45 |
| Message-ID: | 27426.1356286245@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>> This is my first test like this against 9.3 development though, so the cause
>> could be an earlier commit. I'm just starting with the most recent work as
>> the first suspect. Next I think I'll try autovacuum=off and see if the
>> crash goes away. Other ideas are welcome.
> Something like the (untested) debug message below might be helpful:
It might also be interesting to know if there is more than one
still-pinned buffer --- that is, if you're going to hack the code, fix
it to elog(LOG) each pinned buffer and then panic after completing the
loop.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kohei KaiGai | 2012-12-23 18:33:24 | Re: Review of Row Level Security |
| Previous Message | Simon Riggs | 2012-12-23 18:04:51 | Re: Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap [Review] |