On Sat, Apr 30, 2016 at 5:58 AM, Andreas Seltenreich <seltenre...@gmx.de>
> Alvaro Herrera writes:
> > Amit Kapila wrote:
> >> It will be helpful if you can find the offending query or plan
> >> corresponding to it?
> > So I suppose the PID of the process starting the workers should be in
> > the stack somewhere.
> Ja, it's right on the top, but long gone by now…
> > With that one should be able to attach to that process and get another
> > stack trace. I'm curious on whether you would need to have started
> > the server with "postgres -T"
> This sounds like it should work to capture more context when the
> Assertion fails the next time.
Sounds good. So can we assume that you will try to get us the new report
with more information?