On Thu, Mar 28, 2019 at 5:55 AM Andrew Dunstan
<andrew.dunstan@2ndquadrant.com> wrote:
> On 3/27/19 9:48 AM, Tom Lane wrote:
> > Alexander Korotkov <a.korotkov@postgrespro.ru> writes:
> >> Still no reproduction.
> > Annoying, but it's probably not worth expending more effort on
> > right now. I wonder whether that buildfarm animal can be upgraded
> > to capture core dump stack traces --- if so, then if it happens
> > again we'd have more info.
>
> I was able to get this stack trace.
Thank you very much! It appears to be hard to investigate this even
with backtrace. You told you can almost reliably reproduce this.
Could you please, find exact commit caused this error using "git
bisect"? I would very appreciate this.
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
