On Sun, Mar 4, 2018 at 4:37 PM, Thomas Munro <thomas.mu...@enterprisedb.com> wrote: > Could it be that a concurrency bug causes tuples to be lost on the > tuple queue, and also sometimes causes X (terminate) messages to be > lost from the error queue, so that the worker appears to go away > unexpectedly?
Could shm_mq_detach_internal() need a pg_write_barrier() before it writes mq_detached = true, to make sure that anyone who observes that can also see the most recent increase of mq_bytes_written? -- Thomas Munro http://www.enterprisedb.com
