| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: assertion failure 9.3.4 |
| Date: | 2014-04-23 00:19:11 |
| Message-ID: | 535706FF.8030805@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04/22/2014 05:07 PM, Alvaro Herrera wrote:
> If you want to make it easier to reproduce, you need to insert some
> pg_usleep() calls in carefully selected spots. As Andres says, the
> window is small normally.
Yeah, but the whole point of this is that having
pg_stat-statements/auto_explain loaded should make the window much
bigger. In the cases where we're hitting it, we're hitting it with a
fair degree of predicability.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-04-23 00:22:23 | What use case is make_tuple_indirect() supposed to illustrate? |
| Previous Message | Alvaro Herrera | 2014-04-23 00:17:04 | Re: assertion failure 9.3.4 |