| From: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
|---|---|
| To: | "anarazel(at)anarazel(dot)de" <andres(at)anarazel(dot)de> |
| Cc: | 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-26 19:37:45 |
| Message-ID: | 50DB5209.8020101@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/26/12 1:58 PM, anarazel(at)anarazel(dot)de wrote:
> I don't think its necessarily only one buffer - if I read the above output correctly Greg used the suggested debug output which 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(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2012-12-26 19:55:10 | Re: Feature Request: pg_replication_master() |
| Previous Message | anarazel@anarazel.de | 2012-12-26 18:58:54 | Re: buffer assertion tripping under repeat pgbench load |