| From: | Andrew Dunstan <andrew(dot)dunstan(at)pgexperts(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: assertion failure 9.3.4 |
| Date: | 2014-04-21 19:35:18 |
| Message-ID: | 535572F6.3050904@pgexperts.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04/21/2014 03:26 PM, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>> I spent the last two hours poking arounds in the environment Andrew
>> provided and I was able to reproduce the issue, find a assert to
>> reproduce it much faster and find a possible root cause.
> Hmm ... is this the same thing Josh is reporting? If so, why the
> apparent connection with use of pg_stat_statements? Maybe that
> just changes the timing to make the race condition more likely?
>
>
That's my theory. Josh's case is very similar indeed to mine.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-04-21 19:38:03 | Re: assertion failure 9.3.4 |
| Previous Message | Josh Berkus | 2014-04-21 19:31:09 | Re: assertion failure 9.3.4 |