On 2018-Aug-22, Dmitry Dolgov wrote:
> > ENOTIME for a closer look ATM, though, sorry. Maybe you could try
> > running under valgrind?
>
> Could you elaborate please, what can we find using valgrind in this case, some
> memory leaks? In any way there is a chance that everything will be ok, since
> even just a slow tracing under gdb leads to disappearing of this race
> condition.
I don't know. I was thinking it could detect some invalid write in
shared memory.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
